[Webkit-unassigned] [Bug 76214] WebKit supports more of DOM 3 Events than DOMImplementation.hasFeature claims to

[bugzilla-daemon at webkit.org]

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





--- Comment #11 from Eric Seidel <eric at webkit.org>  2012-01-13 14:32:27 PST ---
(In reply to comment #10)
> (In reply to comment #9)
> > I'm not sure "trap" is the right word. :)  I'm fully aware that hasFeature is a bad idea.  I think if we can get it killed, that's the best.  But if it's going to continue to limp along, we should consider making our less completely out of touch.
> 
> Out of touch with what? I'm not sure we can completely kill the feature, but we can stop expanding it and let it be one of the warts that we're stuck with.

The results that hasFeature returns are different from what specs tell us they should, as well as different from FF and IE.

One approach would be simply to make our hasFeature responses exactly match FF or IE, regardless of how they correlate to reality.

Another might be to make our hasFeature always return false.

Another might be to come up with (ask a spec to come up with) the limited set of strings for which we should return "true" and otherwise return false. :)

What I'm saying is this won't be the last time we touch hasFeature.  I'm not seeking to encourage perfect matching of the specs.  (Since we've decided that is a non-goal.) But since perfect matching of the specs is not the goal, we should figure out what the goal is, besides just keeping the code exactly as it happens to be today. :)

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