[Webkit-unassigned] [Bug 76124] WheelEvent.initWebKitWheelEvent differs from DOM Events WheelEvent.initWheelEvent

[bugzilla-daemon at webkit.org]

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


Ojan Vafai <ojan at chromium.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |annevankesteren+webkit at gmai
                   |                            |l.com




--- Comment #8 from Ojan Vafai <ojan at chromium.org>  2012-01-13 19:12:09 PST ---
(In reply to comment #7)
> (In reply to comment #4)
> I mentioned here <https://bugs.webkit.org/show_bug.cgi?id=68791#c14> that casual searching with Code Search indicated that initWheelEvent is used a lot. However we’re in an interesting place, since it obviously isn’t used in WebKit!
> 
> So if the question is one of browser parity compat, I think it makes sense to implement initWheelEvent. (I’m assuming other browsers implement the spec, though.) If the question is about not breaking existing web content, not implementing initWheelEvent makes sense.

Ugh. That's a tough one. I'd be OK with us doing the following:
a) Figuring out what other browsers implement (not including modern IE).
b) Push back on the spec to have the minimally necessary API for initWheelEvent based off the compat needs of (a).
c) Implement that in WebKit.

> In either case we should implement the DOM4 Events-style WheelEvent constructor.

Yes. And since we don't have backwards compat concerns here, it would be better if we just used a single dictionary as the WheelEvent constructor argument instead of the long list initWheelEvent takes.

In either case, some spec needs to handle the WheelEvent constructor and figure out what is minimally necessary for initWheelEvent.

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