Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512)

Trying to respond to the various bits, but not necessarily in order:

> Do you also prevent authors from calling a function that comes from a removed iframe/window?

Edge does this sort of thing in a lot of cases.  For example, it _will_ prevent authors from calling a function from a navigated-away-from iframe/window.  Not sure about the removed case, but when Gecko tried to prevent those being called as callbacks (e.g. event listeners from a removed iframe set on elements that are in a non-removed iframe) I think we ran into web compat issues.  I would be quite interested in thorough testing of UA behavior around this, though it's moderately off-topic for this issue.

> WebKit and Blink preserve the original document's prototype whereas Firefox and Edge(?) change it.

Did WebKit change the behavior since I last checked?  It used to have gc-dependent behavior here; see https://lists.w3.org/Archives/Public/www-dom/2012OctDec/0149.html

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/512#issuecomment-223581816