40068 2010-06-02 10:25:31 -0700 Second document.write() of external script fails 2022-08-14 14:16:41 -0700 1 1 1 Unclassified WebKit DOM 528+ (Nightly build) All All RESOLVED CONFIGURATION CHANGED P2 Minor --- 1 tonyg webkit-unassigned abarth ahmad.saleem792 ap bfulgham eric rniwa oldest_to_newest 233317 0 tonyg 2010-06-02 10:25:31 -0700 The second document.write() of an external script fails. Here's a minimal test case. This alerts "[object HTMLScriptElement]", "null": <script> document.write('<script src=ignored.js id=foo></scri'+'pt>'); alert(document.getElementById('foo')); document.write('<script src=ignored.js id=bar></scri'+'pt>'); alert(document.getElementById('bar')); </script> I'd expect it to work like writing two inline scripts. This alerts "[object HTMLScriptElement]", "[object HTMLScriptElement]": <script> document.write('<script id=foo></scri'+'pt>'); alert(document.getElementById('foo')); document.write('<script id=bar></scri'+'pt>'); alert(document.getElementById('bar')); </script> 233320 1 tonyg 2010-06-02 10:34:54 -0700 Thinking about this more it makes some sense. The first write causes the parser to be blocked by the external script. While the parser is blocked, the script continues executing. It executes the second document.write(), but its content is parser-blocked. Thus at the point the getElementById('bar') executes, the parsed source does not contain the 'bar' script yet. The only way to fix this would be to pause script execution until the external script executes. It isn't clear to me if that is the way it should work or if this is working as intended. Perhaps HTML5 defines this behavior? Thoughts? 233357 2 eric 2010-06-02 11:31:37 -0700 Is this HTML5 only? 233360 3 tonyg 2010-06-02 11:33:04 -0700 This is without the HTML5 parser. I haven't tested it with HTML5.(In reply to comment #2) > Is this HTML5 only? This is without HTML5. I haven't tried it with the HTML5 parser. 233363 4 eric 2010-06-02 11:34:51 -0700 We should attach your test case to this bug, and see what the results are in firefox/IE. This behavior may or may not be expected. 233386 5 57680 tonyg 2010-06-02 12:25:26 -0700 Created attachment 57680 Testcase IE8: PASS Opera 10.5: PASS FF3.6: RACE (passes reliably if an alert is placed after first write) WebKit: FAIL 1887793 6 ahmad.saleem792 2022-07-29 16:59:57 -0700 All browsers (Safari 15.6, Chrome Canary 106 and Firefox Nightly 105 on macOS 12.5) match with each other in the attached test case and show "FAIL". I am not sure on web-spec whether all browsers were wrong or it is just wrong behaviour across all b browsers but just wanted to share latest test results. Thanks! 1891257 7 ap 2022-08-14 14:16:41 -0700 The test itself is now broken, as the written scripts don't show up in the DOM until later. But they do, and can be seen in Web Inspector in all browsers. Still, this is fixed (config changed). 57680 2010-06-02 12:25:26 -0700 2010-06-02 12:25:26 -0700 Testcase doublewrite.html text/html 498 tonyg PGh0bWw+Cjxib2R5PgpUZXN0cyB0aGUgYmVoYXZpb3Igb2Ygd3JpdGluZyB0d28gZXh0ZXJuYWwg c2NyaXB0IGJsb2Nrcy4gU2hvdWxkIHByaW50ICdQQVNTJy4KPGhyPgoKPHNjcmlwdD4KICAgIHZh ciBmb29TY3JpcHQsIGJhclNjcmlwdDsKICAgIGRvY3VtZW50LndyaXRlKCc8c2NyaXB0IHNyYz1p Z25vcmVkLmpzIGlkPWZvbz48L3NjcmknKydwdD4nKTsKICAgIGZvb1NjcmlwdCA9IGRvY3VtZW50 LmdldEVsZW1lbnRCeUlkKCdmb28nKTsKICAgIGRvY3VtZW50LndyaXRlKCc8c2NyaXB0IHNyYz1p Z25vcmVkLmpzIGlkPWJhcj48L3NjcmknKydwdD4nKTsKICAgIGJhclNjcmlwdCA9IGRvY3VtZW50 LmdldEVsZW1lbnRCeUlkKCdiYXInKTsKCiAgICBpZiAoZm9vU2NyaXB0ICYmIGJhclNjcmlwdCkK ICAgICAgICBkb2N1bWVudC53cml0ZSgnUEFTUycpOwogICAgZWxzZQogICAgICAgIGRvY3VtZW50 LndyaXRlKCdGQUlMJyk7Cjwvc2NyaXB0Pgo8L2JvZHk+CjwvaHRtbD4K