[Bug 10901] Use same parsing for HTML <script> and SVG <script>

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

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |WONTFIX

--- Comment #8 from Ian 'Hixie' Hickson <ian@hixie.ch> 2010-10-11 22:48:58 UTC ---
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, please change the state of this bug to CLOSED. If
you have additional information and would like the editor to reconsider, please
reopen this bug. If you would like to escalate the issue to the full HTML
Working Group, please add the TrackerRequest keyword to this bug, and suggest
title and text for the tracker issue; or you may create a tracker issue
yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: no spec change
Rationale: I'm rejecting this because when Adam and Henri say they're scared,
I'm positively petrified.

However, if you get the buy-in from a plurality of implementors (including Adam
and Henri) to change this, I'm game to do it. I just don't want to do it while
they're not explicitly on board.

Regarding document.write(): the proposal wouldn't allow document.write()
anywhere it's not allowed currently, the only difference is that it would allow
_re-entrant_ document.write() where it is not currently allowed. (Compare how
the "script" end tag is handled in the "text" insertion mode vs the "in foreign
content" insertion mode.)

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Monday, 11 October 2010 22:49:03 UTC