This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 7264 - make <% start a bogus comment
Summary: make <% start a bogus comment
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
Keywords: NE, NoReply
Depends on:
Reported: 2009-08-12 09:50 UTC by Anne
Modified: 2010-10-04 13:58 UTC (History)
5 users (show)

See Also:


Description Anne 2009-08-12 09:50:58 UTC
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.

Comment 1 Ian 'Hixie' Hickson 2009-08-12 11:05:53 UTC
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).
Comment 2 Henri Sivonen 2009-08-12 12:46:00 UTC
I think WONTFIXing this is a bit hasty. Are Trident and WebKit developers willing to remove support?
Comment 3 Henri Sivonen 2009-08-13 07:36:52 UTC
Given , I agree this should be WONTFIX.
Comment 4 Maciej Stachowiak 2010-03-14 14:48:59 UTC
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:

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.