- From: Anne van Kesteren <annevk@opera.com>
- Date: Thu, 15 Jan 2009 16:05:58 +0100
- To: "James Graham" <jgraham@opera.com>, "Sam Ruby" <rubys@us.ibm.com>
- Cc: "HTML WG" <public-html@w3.org>
On Thu, 15 Jan 2009 14:31:06 +0100, James Graham <jgraham@opera.com> wrote: > Sam Ruby wrote: >> HTML5 parsing is defined in terms of the DOM produced. >> If you take a simple HTML page (without xmlns marker attributes), and >> parse it by the Gecko, Presto, or WebKit layout engines's parsers, what >> namespace are the DOM elements produced in? > > null, null, http://www.w3.org/1999/xhtml, respectively. Though for CSS purposes all three treat HTML as being in the (X)HTML namespace last time I checked. >> Providing an option to turn this behavior off (with the option >> defaulting to false) is not something I would see as a problem. > > That would be a "don't comply with the spec" option. Which I will > include if the spec doesn't change. But if people are choosing to ignore > MUST level requirements in the spec for the benefit of their users (even > as an option) it suggests a bug in the spec. Isn't there a simple API that ignores namespaces that people can use? -- Anne van Kesteren <http://annevankesteren.nl/> <http://www.opera.com/>
Received on Thursday, 15 January 2009 15:06:49 UTC