On 9/13/16 3:15 PM, Frederik Braun wrote:
First of all, just to see how much breakage to expect when doing this on the web.
Right, but my question is how you plan to measure that.
So I wonder, is there a code path that we'd always call for DOM access to other window objects than the current global scope (e.g., iframes, popups), which have a data URL?
There's a code path that we always call for access across windows, yes. See cross-compartment proxies.
That codepath knows nothing about data URLs and is rather performance-sensitive.
You _could_ perhaps subclass them in the case when the target compartment comes from a data: URL and get somewhere that way. Again, you'd need to do that without regressing peformance for all cross-window access.
I assume the mere creation of those iframes/popups is possibly less useful.
Probably; we know they get created; what we don't know is how they're used. -Boris _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
