RESOLVED FIXED 16722
Page rendered blank due to difference in handling of HTML comment inside script element
https://bugs.webkit.org/show_bug.cgi?id=16722
Summary Page rendered blank due to difference in handling of HTML comment inside scri...
jonathanjohnsson
Reported 2008-01-03 07:34:31 PST
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.
Attachments
Reduced test case (214 bytes, text/html)
2008-01-03 08:07 PST, Mark Rowe (bdash)
no flags
Mark Rowe (bdash)
Comment 1 2008-01-03 08:07:58 PST
Created attachment 18251 [details] 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".
Mark Rowe (bdash)
Comment 2 2008-01-03 08:09:13 PST
Robert Blaut
Comment 3 2008-02-18 00:51:31 PST
*** Bug 12009 has been marked as a duplicate of this bug. ***
Robert Blaut
Comment 4 2008-02-18 00:59:52 PST
I updated URL since previous site was updated and the problem is not visible on that page any more.
Robert Blaut
Comment 5 2008-02-27 05:17:41 PST
The site has no longer the issue visible.
Alexey Proskuryakov
Comment 6 2009-05-08 10:07:09 PDT
*** Bug 25636 has been marked as a duplicate of this bug. ***
Alexey Proskuryakov
Comment 7 2009-05-08 10:07:53 PDT
According to html5lib, WebKit does what the spec says here.
Alexey Proskuryakov
Comment 8 2009-09-01 10:36:23 PDT
*** Bug 28838 has been marked as a duplicate of this bug. ***
Jerome Leclanche
Comment 9 2009-09-01 11:30:32 PDT
(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.
Alexey Proskuryakov
Comment 10 2009-09-01 12:36:09 PDT
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.
Adam Barth
Comment 11 2010-09-20 02:31:18 PDT
Fixed by the HTML5 parser.
Note You need to log in before you can comment on or make changes to this bug.