[Bug 27558] Specify MouseEvent.which

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27558

--- Comment #3 from Rick Byers <rbyers@chromium.org> ---
This sounds like the always-0 UIEvent.pageX/pageY difference Ted (IE team)
reported caused an actual compatibility issue for them:
https://groups.google.com/a/chromium.org/d/msg/input-dev/4p1XZy_17aw/qi-LQuOtvpcJ

So I think it's worth trying to align the Gecko, Blink, Webkit and Edge
behavior here.

I don't really trust the use-counter data here as a reliable indicator of risk
- I suspect most uses will do just as fine with undefined as they did with 0. 
But I don't have any hard data.  If blink's pageX/pageY change goes smoothly,
then I'd be willing to try moving 'which' as well.

Alternately just standardizing it on UIEvent is the simpler option, so fine
with me also.  It's a little uglier, but 'which' is going to be ugly no matter
what way we look at it.

Ted, any thoughts?

If we can get some agreement between vendors here, then I suggest we make a
concrete pull-request to the UIEvents spec.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Friday, 10 July 2015 13:29:15 UTC