27520 2014-12-04 17:51:03 +0000 Considering returning null rather than throwing for cross-origin frameElement 2015-10-29 10:45:12 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED MOVED https://html.spec.whatwg.org/#navigating-nested-browsing-contexts-in-the-dom [good first bug] P3 normal Unsorted 1 contributor ian annevk bobbyholley ian mike philipj yukishiino contributor oldest_to_newest 115942 0 contributor 2014-12-04 17:51:03 +0000 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 115943 1 bobbyholley 2014-12-04 17:52:30 +0000 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. 116568 2 ian 2014-12-19 19:59:26 +0000 I could go either way. What do other browsers do? 116577 3 bobbyholley 2014-12-19 22:50:35 +0000 (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. 123798 4 yukishiino 2015-10-20 07:12:33 +0000 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? 123799 5 annevk 2015-10-20 07:34:39 +0000 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. 123801 6 philipj 2015-10-20 08:31:22 +0000 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? 123836 7 yukishiino 2015-10-22 07:51:28 +0000 Thanks for updating the spec. Will work on W3C tests and Blink implementation (in my spare time, maybe slow). 123984 8 yukishiino 2015-10-29 10:45:12 +0000 Just FYI, everything has got done.