- From: Lyza Gardner <web-platform-tests-notifications@w3.org>
- Date: Fri, 17 Mar 2017 13:51:25 GMT
- To: public-web-platform-tests-notifications@w3.org
@annevk @mikewest My browsing context texts have been primarily focused on same-origin stuff, but, in squinting at https://html.spec.whatwg.org/multipage/browsers.html#crossoriginproperties-(-o-), it does seem to me that FireFox's behavior here is correct as has been asserted: it (Firefox, correctly) is allowing x-origin access to `location` and its `href` property. Also consistent is that `parent.opener.open()` does _not_ work in FF, as `open` is not a property that can be accessed x-origin (I tried that out for my own curiosity in a few browsers). I ran into something yesterday with FF's treatment of a (same-origin) `opener` when a `parent` browsing context is reused via `window.open` targeting, so this thread piqued my interest as it involved `opener` and `parent`—but they are not related. View on GitHub: https://github.com/w3c/web-platform-tests/pull/2356#issuecomment-287358844
Received on Friday, 17 March 2017 13:51:37 UTC