This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Apparently both WebKit and Trident make <% start a bogus content. The interwebs depends on this and since it is really trivial to make the HTML parser do this I think we should add it. It should of course be an error, etc. Examples: http://www.lex24.ilsole24ore.com/Redazione/Riforma_cpc/Riforma.html http://brand.icxo.com/htmlnews/2007/07/11/919666_1.htm http://yuanyunfu.artron.net/exhibi_2.php?aid=A0000016&wrkid=BRT000000033876 http://blog.pewitt.org/CommentView,guid,56fbd9c0-6c0b-4773-abb7-dafb40fae8a7.aspx
This was intentionally not supported because Gecko didn't do it. When <%...%> leaks through it's usually a sign of a server-side error. I think failing loudly is a feature here. The rendering Gecko does on the first of the URLs below isn't fatal or anything (didn't check the others).
I think WONTFIXing this is a bit hasty. Are Trident and WebKit developers willing to remove support?
Given http://software.hixie.ch/utilities/js/live-dom-viewer/saved/207 , I agree this should be WONTFIX.
This bug predates the HTML Working Group Decision Policy. If you are satisfied with the resolution of this bug, 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 This bug is now being moved to VERIFIED. Please respond within two weeks. If this bug is not closed, reopened or escalated within two weeks, it may be marked as NoReply and will no longer be considered a pending comment.