W3C home > Mailing lists > Public > public-html@w3.org > September 2007

Re: New elements vs. Trident

From: Maciej Stachowiak <mjs@apple.com>
Date: Sun, 16 Sep 2007 17:08:11 -0700
Cc: "public-html@w3.org WG" <public-html@w3.org>
Message-Id: <D96F7AD6-E02A-47B4-9307-C1EC85465D6C@apple.com>
To: Dean Edwards <dean@edwards.name>


On Sep 16, 2007, at 10:01 AM, Dean Edwards wrote:

>
> Maciej Stachowiak wrote:
>> Something like this:
>> <newelement><em>some text</em></newelement>
>> Creates a DOM like this:
>> BODY
>>    NEWELEMENT
>>    EM
>>        #text: some text
>>    /NEWELEMENT
>
>> However, it would be nice to avoid the need for such script hacks.  
>> Can anyone from Microsoft comment on the possibility of fixing the  
>> handling of unknown elements in IE, even well in advance of broader  
>> implementation of HTML5?
>
> For XHTML you can mark up new elements like this:
>
> <html:newelement><em>some text</em></html:newelement>

Namespace hacks are certainly an appealing option, if they can avoid  
the need for script. But how would you make this work in both IE and  
in other browsers (including newer browsers that actually support the  
hypothetical newelement)? Would you conditionally serve as HTML to IE  
and XHTML to other browsers?

Regards,
Maciej
Received on Monday, 17 September 2007 00:08:24 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:38:49 UTC