[whatwg] Parse error for "--" in comment end state?

Hi, Shouldn't the Anything else entry in Comment end state[1] be a parse error? As written, the following is allowed: I thought it shouldn't for compability with the "SGML comments" implementations. [1] http://whatwg.org/specs/web-apps/current-work/#comment1 Regards, Simon Pieters

[whatwg] Markup errors in example

Hi, The example for [1] seems to have a markup error: Progress: 0% Should the start tag be there? In the same example there's also this: < ...which probably should be "". [1] http://whatwg.org/specs/web-apps/current-work/#the-progress Regards, Simon Pieters

[whatwg] Authoring tools and presentational markup

Hi, I've been thinking about authoring tools and presentational markup. Forget my earlier suggesetion to reuse instead of . :-) If and don't represent bold and italics, then authroing tools will most likely use and to represent bold and italics instead. (This is already the case, even w

Re: [whatwg] Test suite: Embedded content

Hi, From: Ian Hickson <[EMAIL PROTECTED]> On Mon, 28 Nov 2005, Simon Pieters wrote: > > I've created a test suite for , , / and > with the data types image/png, text/plain, text/html, > application/xml and application/x-shockwave-flash, with the HTTP > responces 200, 404, 410, 301 to 200, 301 t

[whatwg] Doctype conformance requirements

Hi, The conformance requirements section[1] states that: HTML documents that use the new features described in this specification and that are served over the wire (e.g. by HTTP) must be sent as text/html and must start with the following DOCTYPE: . So, if I read this correctly, HTML docume