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

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Feb 20 01:15:12 PST 2009


------- Comment #19 from jchaffraix at webkit.org  2009-02-20 01:15 PDT -------
(In reply to comment #18)
> (In reply to comment #17)
> > In HTML5, it's the document that has the HTML vs XML flag and an element acts
> > as per its document's flag. It isn't done on a per-element basis.
> WebKit has an equivalent distinction.  document->isHTMLDocument() will tell you
> if your Document* is really an HTMLDocument* and thus you should be in "html"
> mode not XHTML mode.

Exactly. This is the core of my comments: other browsers do such a distinction
on an element level (using the namespace).
HTML5 removes the namespace distinction as HTML and XHTML elements uses the
same namespace and places the distinction at the document level. However the
second change will lead to compatibility bugs (this bug is an example).
I am just stating that my change only solves part of our current compatibility
issue and that we may prefer to solve it entirely, which means a per-element
policy that goes against HTML5. We may also decide that this is just a corner
case and just side with HTML5.

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