16722 2008-01-03 07:34:31 -0800 Page rendered blank due to difference in handling of HTML comment inside script element 2011-03-30 00:28:10 -0700 1 1 1 Unclassified WebKit DOM 523.x (Safari 3) All All RESOLVED FIXED HasReduction, InRadar P1 Normal --- 1 jonathanjohnsson webkit-unassigned abarth ap chinmaya dbates jasneet jerome jgjedi mrowe webkit oldest_to_newest 66128 0 jonathanjohnsson 2008-01-03 07:34:31 -0800 Going to http://www.skype.com/allfeatures/callphones/ shows a blank page. Firefox shows the page as expected. The same happens both in released Safari 3.04 and in nightly r29120. 66129 1 18251 mrowe 2008-01-03 08:07:58 -0800 Created attachment 18251 Reduced test case The erroneous behaviour is triggered by the following snippet: <script type="text/javascript"> //<!--[CDATA[ //]]> </script> <!-- Extra comment --> Firefox sees the initial comment as ending inside the script element, while WebKit treats it as extending past "Extra comment". 66130 2 mrowe 2008-01-03 08:09:13 -0800 <rdar://problem/5668296> 71013 3 webkit 2008-02-18 00:51:31 -0800 *** Bug 12009 has been marked as a duplicate of this bug. *** 71014 4 webkit 2008-02-18 00:59:52 -0800 I updated URL since previous site was updated and the problem is not visible on that page any more. 72135 5 webkit 2008-02-27 05:17:41 -0800 The site has no longer the issue visible. 120437 6 ap 2009-05-08 10:07:09 -0700 *** Bug 25636 has been marked as a duplicate of this bug. *** 120438 7 ap 2009-05-08 10:07:53 -0700 According to html5lib, WebKit does what the spec says here. 143935 8 ap 2009-09-01 10:36:23 -0700 *** Bug 28838 has been marked as a duplicate of this bug. *** 143953 9 jerome 2009-09-01 11:30:32 -0700 (In reply to comment #7) > According to html5lib, WebKit does what the spec says here. "View source" doesn't actually show the entire source. While it may be intended, the parser dying should be fixed. 143978 10 ap 2009-09-01 12:36:09 -0700 1. Safari "View Source" does show the entire source. 2. What do you mean by "parser dying"? A crash? Since we do what HTML5 tells us to do, the most direct route forward is to discuss this issue with WhatWG or W3C HTML5 work groups. 281460 11 abarth 2010-09-20 02:31:18 -0700 Fixed by the HTML5 parser. 18251 2008-01-03 08:07:58 -0800 2008-01-03 08:07:58 -0800 Reduced test case bug-16722.html text/html 214 mrowe PGh0bWw+Cjxib2R5PgoKPHNjcmlwdCB0eXBlPSJ0ZXh0L2phdmFzY3JpcHQiPgovLzwhLS1bQ0RB VEFbCi8vXV0+Cjwvc2NyaXB0PgoKPHA+RmlyZWZveCByZW5kZXJzIHRoaXMgYXMgdmlzaWJsZS48 L3A+Cgo8IS0tIFdlYktpdCBzZWVzIHRoZSBjb21tZW50IGluc2lkZSB0aGUgc2NyaXB0IGVsZW1l bnQgYXMgZW5kaW5nIGhlcmUgPT0+IC0tPgoKPC9ib2R5Pgo8L2h0bWw+Cg==