On Thu Nov 20 16:34:22 2025 +0000, Gabriel Ivăncescu wrote:
I had a deeper look, there's a couple issues if we go that route:
- `find_dispid` would be overzealous and also apply it to prototypes
and stub constructors (in dispex.c), while they don't have volatile props. Relying only on `get_dispid` isn't perfect either, since then Window won't be marked as having volatile props. I guess we could use a flag on top of just checking for `get_dispid` but... 2. Object elements (and plugin containers) aren't volatile since they cache the props now, but would be marked as such. So what should I do?
That's fine then, thanks.