W3C home > Mailing lists > Public > whatwg@whatwg.org > September 2006

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

From: Lachlan Hunt <lachlan.hunt@lachy.id.au>
Date: Sun, 10 Sep 2006 23:40:24 +1000
Message-ID: <450415C8.5070806@lachy.id.au>
Dave Raggett wrote:
> You can reproduce my tests by pointing your browser at:
> 
>   http://people.w3.org/~dsr/dom/test.html

OK, I have the discovered the reason for the discrepancy in our results. 
  Apparently IE handles exactly the same markup differently depending 
upon how it is added to the page.

If you load my test case [1] in IE, tests A through E are styled, but 
test F isn't.  This shows the following:

IE will only allow styling of elements with namespace prefixes that have 
been either explicitly or implicitly declared.

There are two ways to explicitly declare a namespace in IE:
1. <html xmlns:foo="http://example.org/foo">
2. <?xml:namespace prefix = foo ns = "http://example.org/foo" />

In both cases, the URI may be omitted.

When a "Custom Tag" (the name Microsoft have given elements with 
namespace prefixes in HTML) is added using either innerHTML or 
document.write(), the PI that declares the namespace will be implicitly 
generated using the prefix but with no actual namespace name.

This explains why I was getting different results using the Live DOM 
Viewer because it uses innerHTML to copy the markup from the text box to 
the rendering area.  That means that IE was implicitly declaring the 
namespace of all Custom Tags in my tests.

[1] http://lachy.id.au/dev/2006/09/custom-tags

-- 
Lachlan Hunt
http://lachy.id.au/
Received on Sunday, 10 September 2006 06:40:24 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:29 UTC