[Webkit-unassigned] [Bug 36465] window.Document !== window.XMLDocument

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=36465





--- Comment #24 from Adam Barth <abarth at webkit.org>  2010-03-23 16:25:33 PST ---
Do you have an alternative proposal for resolving Bug 9063?

> The Firefox document hierarchy looks and feels obsolete since HTML elements
> became the same as XHTML ones in DOM. I don't think XMLDocument a reasonable
> thing to expose now.

This sounds more like an aesthetic argument.  I agree that this solution is
rather unaesthetic, but I don't know of another workable solution.

> > (B) proven compatibility with web content for the better part of a decade.
> 
> This is true to some extent, but matching other browsers has been also known to
> introduce unexpected compatibility problems due to enabling different code
> paths. E.g., document.all had an even better historical compatibility story,
> but there was no way we could enable it without making it undetectable.

I would be surprised if that were the case here.  These perils exist more often
when matching IE.  In this case, I'm suggesting we match the behavior that
Firefox has had since 2001.

In particular, Bug 9063 is the most common WebKit compatibility issue I run
into personally.  I've run across it several times in the past few months and
have had to use Firefox to access some web sites.  I don't really understand
the resistance to fixing this bug.

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