W3C home > Mailing lists > Public > whatwg@whatwg.org > August 2013

Re: [whatwg] Namespaces and tag names in the HTML parser

From: Ian Hickson <ian@hixie.ch>
Date: Thu, 1 Aug 2013 17:31:41 +0000 (UTC)
To: Peter Occil <poccil14@gmail.com>
Message-ID: <alpine.DEB.2.00.1307312259550.9685@ps20323.dreamhostps.com>
Cc: WHATWG <whatwg@whatwg.org>
On Wed, 10 Jul 2013, Peter Occil wrote:
> >
> > Short of explicitly putting "in the HTML namespace" at every 
> > occurrence of this, I don't know how to fix this. Putting "in the HTML 
> > namespace" everywhere is a non-starter, there's something like ten 
> > thousand occurrences of element names in the spec. (Literally. Ten 
> > thousand.)
> 
> I don't mean in the entire HTML spec, I only mean within the tree 
> construction section, and then only where it eliminates ambiguity, such 
> as "while the current node is not a tr element or an html element", as I 
> stated previously.  I agree it's silly to include the words "in the HTML 
> namespace" everywhere in the spec.

I don't really understand why that case is ambiguous, but thousands of 
others aren't. Can you elaborate on what the difference is?

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Thursday, 1 August 2013 17:32:06 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:09:23 UTC