W3C home > Mailing lists > Public > whatwg@whatwg.org > February 2008

[whatwg] [Whatwg] Parsing: Greater-than characters in doctype

From: Simon Pieters <simonp@opera.com>
Date: Thu, 14 Feb 2008 12:00:12 +0100
Message-ID: <op.t6igumesidj3kv@hp-a0a83fcd39d2.belkin>
On Thu, 14 Feb 2008 06:18:58 +0100, Ian Hickson <ian at hixie.ch> wrote:

> I looked into these, and frankly, I'm reluctant to add them to the spec.  
> I
> haven't seen a huge number of sites that depend on these, and the other
> browsers don't seem to particularly require it.
> Unless someone has a good reason to do otherwise, I say we skip this.

That makes sense, but, then I'd like doctypes to be closed at the first >  
even if it's in a FPI or SI, to match Opera, Safari and Firefox, and to  
allow implementations to do doctype analysis in the parser stage instead  
of in the tokenizer stage should they so wish, or skip doctype analysis  
altogether if it is of no interest to them...

i.e., I'd like the > character in these states:

    DOCTYPE public identifier (double-quoted) state
    DOCTYPE public identifier (single-quoted) state
    DOCTYPE system identifier (double-quoted) state
    DOCTYPE system identifier (single-quoted) state

...to be a parse error, mark the doctype as incorrect, emit the token, and  
switch to the data state.

Simon Pieters
Opera Software
Received on Thursday, 14 February 2008 03:00:12 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:00 UTC