On Wed Nov 19 18:48:57 2025 +0000, Jacek Caban wrote:
Could we just set the flag based on the presence of `get_dispid`/`find_dispid` in `init_host_object` instead of specifying it separately? That’s fine if we have use cases that need a different condition, but for this patch it doesn’t seem necessary.
I had a deeper look, there's a couple issues if we go that route:
1. `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?