[Webkit-unassigned] [Bug 17167] Failures in fast/dom/Node/initial-values.html

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Feb 18 04:19:30 PST 2009


jchaffraix at webkit.org changed:

           What    |Removed                     |Added
  Attachment #27655|review+                     |
               Flag|                            |

------- Comment #13 from jchaffraix at webkit.org  2009-02-18 04:19 PDT -------
(From update of attachment 27655)
Sorry to reply to the discussion this late.

I had the same thoughts as Eric about the specification.
Document.createElementNS will create an XHTML element per DOM spec (as it
splits the localName to fill the prefix which is not done in HTML). To be
consistent with the DOM then we also need to have Element.nodeName match the
XHTML behaviour. This is also what the other browser are doing.

As we do not have a way to know whether an HTMLElement represents internally an
XHTML element, the prefix check will correct at least part of the issue
(non-prefixed element will continue to fail).
Clearing the review flag as I would like to update the test and the code to
account for this.

Configure bugmail: https://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.

More information about the webkit-unassigned mailing list