W3C home > Mailing lists > Public > public-html@w3.org > January 2009

Re: Placing elements in the HTML namespace

From: Maciej Stachowiak <mjs@apple.com>
Date: Thu, 15 Jan 2009 18:44:39 -0800
Cc: Anne van Kesteren <annevk@opera.com>, HTML WG <public-html@w3.org>
Message-id: <67000190-B4BD-4A1E-9D97-617BD1C32C1D@apple.com>
To: Boris Zbarsky <bzbarsky@mit.edu>


On Jan 15, 2009, at 7:34 AM, Boris Zbarsky wrote:

>
> Anne van Kesteren wrote:
>> Though for CSS purposes all three treat HTML as being in the  
>> (X)HTML namespace last time I checked.
>
> Right.  Gecko has a concept of "html element" that is distinct from  
> the namespace, and this is used to force such elements to match CSS  
> selectors in the XHTML namespace.
>
> However, there are two differences between XHTML and HTML in Gecko  
> last I checked (in 2005, but I don't think we've changed these):
>
> 1)  frames/iframes.  For XHTML we use the id attribute value as the
>    window name, for HTML we use the name attribute value.  Should this
>    be based on the document type instead?  Or something else?
> 2)  Serializing XML -- for XHTML we set shorthand attrs to be
>    |foo="foo"| while for HTML we set them to just be |foo|.
>    This only affects people calling the XML serializer on a DOM coming
>    from text/html, but that sounds like something HTML5 wants to
>    support.

In WebKit we implement all HTML/XHTML differences based on whether the  
containing document is an HTML or XML document. The element objects  
themselves are indistinguishable.

Regards,
Maciej
Received on Friday, 16 January 2009 02:45:51 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:00 UTC