Named access on the window object has the wrong value for iframes
Reported by
matt...@bitovi.com,
Jun 22 2016
|
||||
Issue description
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.84 Safari/537.36
Example URL:
Steps to reproduce the problem:
Create a page with this html:
<iframe id="foo"></iframe>
<script>
console.log(window.foo === document.getElementById('foo'));
</script>
What is the expected behavior?
It should log "false"
What went wrong?
It logs "true" instead.
Does it occur on multiple sites: N/A
Is it a problem with a plugin? N/A
Did this work before? N/A
Does this work in other browsers? N/A
Chrome version: 51.0.2704.84 Channel: n/a
OS Version: OS X 10.11.3
Flash Version: Shockwave Flash 22.0 r0
For iframes the global should be it's contentWindow per the spec: https://html.spec.whatwg.org/#dom-window-nameditem
This works correctly in Safari.
,
Jun 23 2016
For reference, I also filed this with Firefox and they believe it to be an invalid bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1281604
,
Jun 24 2016
,
Jun 26 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 26 2017
I believe this is a WontFix. This is the opposite bug to issue 171873.
,
Jun 29 2017
I agree with phistuck@. This is an expected behavior. |
||||
►
Sign in to add a comment |
||||
Comment 1 by brajkumar@chromium.org
, Jun 23 2016Labels: M-53 OS-Linux OS-Windows
Status: Untriaged (was: Unconfirmed)