This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
This was was cloned from bug 16945 as part of operation convergence. Originally filed: 2012-05-05 20:57:00 +0000 Original reporter: Raj Doshi <admin@tacosw.com> ================================================================================ #0 Raj Doshi 2012-05-05 20:57:45 +0000 -------------------------------------------------------------------------------- In the "Script data escaped less-than sign state" for tokenization (section 8.2.4.25), there is an error in the "Anything Else" case. It currently says "Switch to the script data state." It should say "Switch to the script data escaped state" since the escaping "<!--" is still applicable. ================================================================================ #1 Simon Pieters 2012-05-07 08:58:48 +0000 -------------------------------------------------------------------------------- Indeed! http://software.hixie.ch/utilities/js/live-dom-viewer/saved/1511 It seems Opera/WebKit/Gecko already do this. ================================================================================
The theory here is that if the spec was right, then these two would render the same ("x"): http://software.hixie.ch/utilities/js/live-dom-viewer/saved/1808 http://software.hixie.ch/utilities/js/live-dom-viewer/saved/1511 ...but because they don't, the spec is wrong, right? My head hurts.
Checked in as WHATWG revision r7420. Check-in comment: Make the parser match the implementations (and not be more even more crazy than necessary). http://html5.org/tools/web-apps-tracker?from=7419&to=7420