185243 2018-05-03 01:50:32 -0700 iframe.contentWindow.document not accessible only on WebKit. 2018-05-03 13:29:42 -0700 1 1 1 Unclassified WebKit DOM WebKit Nightly Build Unspecified Unspecified RESOLVED DUPLICATE 11388 https://bugs.webkit.org/show_bug.cgi?id=11388 https://html.spec.whatwg.org/multipage/window-object.html#named-access-on-the-window-object P2 Normal --- 1 emilio cdumez ajuma cdumez danyao sam oldest_to_newest 1420060 0 339399 emilio 2018-05-03 01:50:32 -0700 Created attachment 339399 test.html See the testcase incoming, which does something useful in every other browser. 1420115 1 danyao 2018-05-03 07:39:25 -0700 The problem doesn't seem to be with iframe.contentWindow.document. If I just add "var frm = document.getElementById('frm');" at the beginning, WebKit behaves identically to Chrome. I don't think it's standard to be able to reference HTML element by ID as named variables in JavaScript. I could be wrong. 1420146 2 ajuma 2018-05-03 09:10:19 -0700 (In reply to Danyao Wang from comment #1) > The problem doesn't seem to be with iframe.contentWindow.document. If I just > add "var frm = document.getElementById('frm');" at the beginning, WebKit > behaves identically to Chrome. > > I don't think it's standard to be able to reference HTML element by ID as > named variables in JavaScript. I could be wrong. See bug 183087; the id becomes a global variable unless it gets shadowed by another explicitly declared global variable. So if adding "var frm = document.getElementById('frm');" changes behavior in this example, that sounds like a bug, since frm should already be referring to that element. 1420157 3 cdumez 2018-05-03 09:27:57 -0700 I believe the issue is that WebKit wrongly uses the iframe's id as the iframe's window name. Because of the ordering of Window's named property getter, we return the iframe's window that matches 'frm' instead of the iframe with id 'frm'. 1420181 4 cdumez 2018-05-03 09:53:08 -0700 (In reply to Chris Dumez from comment #3) > I believe the issue is that WebKit wrongly uses the iframe's id as the > iframe's window name. Because of the ordering of Window's named property > getter, we return the iframe's window that matches 'frm' instead of the > iframe with id 'frm'. Ironically, looks like I fixed this in Blink a long time ago :) https://bugs.chromium.org/p/chromium/issues/detail?id=347169 1420212 5 cdumez 2018-05-03 10:37:07 -0700 *** This bug has been marked as a duplicate of bug 11388 *** 1420217 6 emilio 2018-05-03 10:45:19 -0700 (In reply to Chris Dumez from comment #4) > (In reply to Chris Dumez from comment #3) > > I believe the issue is that WebKit wrongly uses the iframe's id as the > > iframe's window name. Because of the ordering of Window's named property > > getter, we return the iframe's window that matches 'frm' instead of the > > iframe with id 'frm'. > > Ironically, looks like I fixed this in Blink a long time ago :) > https://bugs.chromium.org/p/chromium/issues/detail?id=347169 Lol. Ok, thanks a lot, now I can report the CSS bug I really wanted to report :-) 339399 2018-05-03 01:50:32 -0700 2018-05-03 01:50:32 -0700 test.html test.html text/html 669 emilio PCFET0NUWVBFIGh0bWw+CjxpZnJhbWUgaWQ9ImZybSIgc3R5bGU9IndpZHRoOiAxMDBweDsgaGVp Z3RoOiAxMDBweCI+PC9pZnJhbWU+Cjxicj4KPHNjcmlwdD4KICB2YXIgZnJtRG9jID0gZnJtLmNv bnRlbnRXaW5kb3cuZG9jdW1lbnQ7CiAgZnJtRG9jLm9wZW4oKTsKICBmcm1Eb2Mud3JpdGUoJzxi b2R5PklycmVsZXZhbnQ8L2JvZHk+Jyk7CiAgZnJtRG9jLmNsb3NlKCk7CgogIGRvY3VtZW50LmJv ZHkub2Zmc2V0VG9wOwoKICBpZiAoZnJtLmNvbnRlbnRXaW5kb3cubWF0Y2hNZWRpYSgnKG1heC13 aWR0aDogMTUwcHgpJykubWF0Y2hlcykKICAgIGRvY3VtZW50LndyaXRlKCJQQVNTPGJyPiIpOwog IGVsc2UKICAgIGRvY3VtZW50LndyaXRlKCJGQUlMIC0gTWVkaWEgZGlkbid0IG1hdGNoPGJyPiIp CgogIGZybS5zdHlsZS53aWR0aCA9ICIyMDBweCI7CgogIC8vIFVuY29tbWVudCB0byBwYXNzOgog IC8vIGZybURvYy5kb2N1bWVudEVsZW1lbnQub2Zmc2V0VG9wOwoKICBpZiAoZnJtLmNvbnRlbnRX aW5kb3cubWF0Y2hNZWRpYSgnKG1heC13aWR0aDogMTUwcHgpJykubWF0Y2hlcykKICAgIGRvY3Vt ZW50LndyaXRlKCJGQUlMIC0gTWVkaWEgaW5jb3JyZWN0bHkgbWF0Y2hlZDxicj4iKQogIGVsc2UK ICAgIGRvY3VtZW50LndyaXRlKCJQQVNTPGJyPiIpOwo8L3NjcmlwdD4K