This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: https://html.spec.whatwg.org/ Multipage: https://html.spec.whatwg.org/multipage/#navigating-nested-browsing-contexts-in-the-dom Complete: https://html.spec.whatwg.org/#navigating-nested-browsing-contexts-in-the-dom Referrer: Comment: Considering returning null rather than throwing for cross-origin frameElement Posted from: 12.216.224.110 User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:37.0) Gecko/20100101 Firefox/37.0
This is what Gecko does now - it seems reasonable and symmetric, given that we also return null for cross-origin .contentDocument. Any reason not to return null instead of throwing? I'm totally willing to change Gecko's behavior if we decide for some reason that it's undesirable.
I could go either way. What do other browsers do?
(In reply to Ian 'Hixie' Hickson from comment #2) > I could go either way. What do other browsers do? Chrome throws. I can't figure out how to make Safari's web console change contexts to the iframe, and I don't have time to write an actual test.
I happened to know this issue, and I'm now thinking that returning null is preferable. If this is going to be spec'ed, I'm happy to implement the new behavior in Chrome. What's the situation? What's preventing to update the spec?
We just need someone to provide a patch to the specification or one of the editors to get around to it. See https://github.com/whatwg/html for details.
I've attempted to fix this in https://github.com/whatwg/html/pull/266 Shiino-san, can you update http://w3c-test.org/html/browsers/windows/nested-browsing-contexts/frameElement.sub.html and import that test into Blink when you implement the new behavior?
Thanks for updating the spec. Will work on W3C tests and Blink implementation (in my spare time, maybe slow).
Just FYI, everything has got done.