[whatwg] Hacking away on forms ... (fwd)

Anne van Kesteren fora at annevankesteren.nl
Sat Sep 9 09:00:15 PDT 2006

On Fri, 08 Sep 2006 18:40:34 +0200, Dave Raggett <dsr at w3.org> wrote:
> p.s. implementing the output element would be a lot cleaner if more  
> browsers supported the /> syntax for empty elements that aren't part of  
> traditional HTML. IE already does so, but Firefox and Opera do not.  
> Firefox is even worse as it coerces the tag name to upper case when you  
> inspect the DOM node it creates! Opera and Firefox also differ over the  
> amount of whitespace text nodes that are set as the content on unknown  
> elements. IE has its own weird worts, although strangely, it works  
> rather nicely for non-html markup in XML namespaces. IE therefore  
> encourages the use of XML namespaces for mixed markup when delivered as  
> text/html.

You sure IE only does this for <foo/> and not also for <foo>? It's my  
understand they are treated as being identical in every single browser.  
Whether or not such an element is treated as empty varies from browser to  

Converting the node name to uppercase also seems like the right thing to  
do for text/html documents although HTML5 might change bits of that...

Anne van Kesteren

More information about the whatwg mailing list