[Webkit-unassigned] [Bug 8007] createElement() and XHTML (A dynamically created table not rendered as such)

[bugzilla-daemon at webkit.org]

http://bugs.webkit.org/show_bug.cgi?id=8007





------- Comment #21 from robburns1 at mac.com  2007-08-14 20:39 PDT -------
Does anyone know how IE processes document.createElement in XML with and
without namespaces? I'd imagine that if IE ever gets around to adding XHTML
support it might follow the same approach that it already uses (perhaps that's
how the DOM recommendation ended up so strange). 

BTW, I notice that none of the relevant language on this uses any normative
phrases. This may be an oversight by the authors, but that shouldn't be the
only assumption in reading this. Its quite possible the authors deliberately
left the normative language out of the recommendation on this issue. If that is
the case, they may have simply been trying to discuss issues of concern to DOM
users and not telling implementations how to handle these things. That may be
bad for interoperability, but that's where we find ourselves. Just for easy
reference here are the two most relevant places I found discussing the issue in
the recommendation:

http://www.w3.org/TR/2004/REC-DOM-Level-3-Core-20040407/core.html#ID-2141741547

http://www.w3.org/TR/2004/REC-DOM-Level-3-Core-20040407/core.html#Namespaces-Considerations

In particular:

"The "NS" methods, such as Document.createElementNS(namespaceURI,
qualifiedName) and Document.createAttributeNS(namespaceURI, qualifiedName), are
meant to be used by namespace aware applications. Simple applications that do
not use namespaces can use the DOM Level 1 methods, such as
Document.createElement(tagName) and Document.createAttribute(name). Elements
and attributes created in this way do not have any namespace prefix, namespace
URI, or local name."


-- 
Configure bugmail: http://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.