W3C home > Mailing lists > Public > public-html@w3.org > April 2008

Re: [whatwg] Exploring new vocabularies for HTML

From: Thomas Broyer <t.broyer@gmail.com>
Date: Sat, 5 Apr 2008 18:05:22 +0200
Message-ID: <a9699fd20804050905j658552c4ua0de910afec0f63d@mail.gmail.com>
To: "Ian Hickson" <ian@hixie.ch>, public-html@w3.org
To add to the discussion, here are small tests of IE's "namespace support":
http://www.ltgt.net/ie-namespace-tests.html
I've run the tests on IE7 on Vista, IE6 on WinXP SP2 (Virtual PC image
from Microsoft) and IE8b1 on WinXP SP2 (Virtual PC image from
Microsoft), the results are exactly the same.

What's noticeable:
 - <:foo /> is not parsed as an element (it will appear verbatim as if
it had been written &lt;:foo /&gt;)
 - As soon as there is a colon in the element's name (even at the very
end: <foo: />), "/>" is recognized and signals an empty element (note
that HTML --unprefixed-- elements within the subtree don't inherit
this parsing trick: <B/> is parsed as <B>).
 - xmlns "declaractions" are not recognized if the associated "prefix"
contains a colon (xmlns:baz:quux)
 - prefixes are matched case-insensitively
 - as soon as an element is prefixed with a declared namespace, its
tagName's case is preserved. The tagName becomes the unprefixed tag
name, tagUrn is set to the value of the "xmlns declaration", and
scopeName is set to the "namespace prefix" (it equals "HTML"
otherwise, while tagUrn "defaults" to the empty string).
 - The "namespace support" does not change the way unmatched tags are parsed.
 - getElementsByTagName matches case-insensitively on tagNames (i.e.
without the prefix)

On Tue, Mar 25, 2008 at 1:25 AM, Thomas Broyer wrote:
> On Mon, Mar 24, 2008 at 9:58 PM, Ian Hickson wrote:
> >
> > I've started trying to distill problem descriptions out of the 367 e-mails
> > about using markup from namespaces other than HTML in text/html that are
> > currently in the WHATWG Issues List. [1]
> >
> > I'm putting what I find into a page on the WHATWG wiki. [2]
> >
> > If anyone wants to help out, please coordinate with me on #whatwg on
> > Freenode IRC or #html-wg on W3C IRC, or drop me an e-mail.
>
> FYI, I've started some work in html5lib (in the
> namespaces-in-text-html branch [1]).
> For the moment, it (almost) mimics IE5.5/IE6/IE7 behavior (except that
> it doesn't deal with xmlns attributes at all).
>
> I could summarize the changes from the spec and what I intend to do
> (to support default namespace, and create elements in the appropriate
> namespaces –i.e. deal with xmlns attributes–) if you want to.
>
> It seems Anne also started some work (he created an svg+math branch);
> and I intend to port my changes to Twintsam (which codebase I know
> much more than html5lib's one ;-) )
>
> [1] http://html5lib.googlecode.com/svn/branches/namespaces-in-text-html/
>
> --
> Thomas Broyer
>



-- 
Thomas Broyer
Received on Saturday, 5 April 2008 16:05:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:16:14 GMT