On Wed Nov 9 16:36:36 2022 +0000, Jacek Caban wrote:
This breaks COM rule: it's possible that we'd return IEventTarget in one QI call, then navigate to other page and then return failure for QI on the same object. We avoid this problem for document node by locking compat mode, but this won't work here, because doc_node may change as a result of navigation to other page. Do you know if native also breaks those rules? It would be also interesting to know what happens to registered events in this case: if we register an event handler on document object and then document node changes, should those events handlers still work or are they dropped (they will be dropped with this patch)?
Good point, I haven't really tested that, mostly because I don't know how to write a proper test that navigates to a different doc node on same doc obj. Do you have tips or should I just test it "manually"?