This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
>>>>> User agents must use these rules for resources that >>>>> have the text/html media type. Here is an example document that >>>>> conforms to the HTML syntax: >>>> >>>> I'm not sure why this example is here? What does this have to do with >>>> parsing? How is the parsing of this document any different from HTML4? >>> >>> It illustrates what was just explained. The DOCTYPE is different. <meta >>> charset> is too. >> >> Ok, then please add "(note the differences in <doctype> and <meta >> charset>)." >> >> Better yet, you should have a side by side comparison of the two. You >> could make the distinction much more clear if you showed a minimally >> conforming document, like this: >> >> <!doctype html> >> <html> >> <meta charset="UTF-8"> >> <title>Example document</title> >> <p>Example paragraph >> >> The above example totally valid/conforming >> (http://html5.validator.nu/) and really illustrates the differences - >> and gets rid of all those redundant closing tags! > > HTML4 allowed that too so you have the same amount of differences. I tried the above in both validator.nu and validator.w3.org and both reported it to be invalid HTML4.1 (all flavors of it). >> > I > don't think detailed comparison of these differences is interesting. > This is enough for authors to just copy and paste and that is probably > the most useful bit of that section. I disagree. I think it is particularly interesting because it demonstrates the disconnect between markup and DOM, which is an inherent difference between the two languages (i.e., HTML5 is defined in terms of the DOM and without understanding the DOM construction algorithm, you are quickly gonna get into problems... while, HTML4 seems to be DOM agnostic or something. Anyway, important difference - be nice to see it in the document.). >>> This document is not intended for such depth. >> >> Ok, at least make sure you link to the relevant section in HTML5. > > I'm only doing that for the elements at the moment. Maybe once we go to > CR or something stable like that I could add a bunch more links. Ok, can you add a note to the spec stating that... so you won't forget:)
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.