This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
>>>> for this syntax which are largely compatible with popular >>>>> implementations. >>>> >>>> Please reference the implementations on which the parsing is based. >>>> And please explain why those implementations (be it browser or search >>>> engine) were chosen as the basis on which the parsing algorithm was >>>> based on. >>> >>> I don't think this is of relevance to this document, but it would sure >>> be interesting. >> >> I disagree. It's common knowledge that parsing is mostly based on IE6. >> I don't see the problem with mentioning IE6 there. >> >> If the common knowledge is wrong, then this is the document that has >> to set the record straight. > > As I explained before this document is not about explaining how HTML5 > design decisions were arrived at. I'm asking you to make a statement of fact, not to explain how the fact was derived. so you could say "this syntax which are largely compatible with popular implementations because it is largely based on Internet Explorer 6's behavior." It's important to document history here: without it, we are bound to make the same mistakes again. If other implementation played a role (e.g., the way Google's spiders process pages), then those should be documented too.
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: Agreed with reporter in private email to close this bug.