W3C home > Mailing lists > Public > public-html@w3.org > January 2009

[Bug 6357] New: <script> start tag parsing

From: <bugzilla@wiggum.w3.org>
Date: Mon, 05 Jan 2009 16:28:33 +0000
To: public-html@w3.org
Message-ID: <bug-6357-2495@http.www.w3.org/Bugs/Public/>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=6357

           Summary: <script> start tag parsing
           Product: HTML WG
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Spec bugs
        AssignedTo: dave.null@w3.org
        ReportedBy: annevk@opera.com
         QAContact: public-html-bugzilla@w3.org
                CC: ian@hixie.ch, mike@w3.org, public-html@w3.org


Both Presto and WebKit currently handle a self-closing flag on a <script>
element start tag in a special way.

In WebKit it always pops the element of the stack.

In Presto it pops the element of the stack if a src attribute with a non-empty
value is also present.

Gecko and Trident do not handle the flag in a special way.

WebKit style parsing breaks at least this page:
http://www.google.com/codesearch/p?hl=en#fYNO89zotsk/sahana-phase1/damagereg/web/Login.jsp&q=%3Cscript[^%3E]*/%3E

It is unfortunately near impossible for Opera and WebKit to change behavior
drastically due to deployed Dashboard and Opera widgets. (Introducing
differences between Web page and widget rendering would be theoretically
possible (and admittedly WebKit has done this for <canvas>), but is not
desirable.)

I would like to do more research into what pages would break and which would
work better, but unfortunately Philips' tool cannot be used.


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Monday, 5 January 2009 16:28:43 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:16:28 GMT