New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 699865 link

Starred by 3 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocking:
issue 674593


Show other hotlists

Hotlists containing this issue:
Non-Standard-IDL


Sign in to add a comment

Standardize or remove WheelEvent#wheelDelta/wheelDeltaX/wheelDeltaY

Project Member Reported by foolip@chromium.org, Mar 9 2017

Issue description

These three attributes exist in Chromium, EdgeHTML and WebKit.

Standardization seems like the best path, so:
https://github.com/w3c/uievents/issues/138
 
Cc: foolip@chromium.org
Labels: Hotlist-Input-Dev
Owner: dtapu...@chromium.org
Status: Assigned (was: Untriaged)

Comment 3 by mustaq@chromium.org, May 16 2017

The spec discussion seems to suggest documenting the behavior diffs without either standardization or removal, right?  IMO that doesn't make the web platform better in any way.  Given the wide diffs in implementations, may be we should just try removing it?

Comment 4 by foolip@chromium.org, May 29 2017

Are there alternative APIs that can be used for the same things as these attributes? If there aren't, then I think the best next step would be to look a bit closer at the exact behavior of Chrome, Edge and Safari. Per https://github.com/w3c/uievents/issues/138#issuecomment-285261522 it's still an unknown whether content depends on the differences, so standardizing some intersection of behavior could still be possible.
Labels: Hotlist-Interop
Owner: nzolghadr@chromium.org

Sign in to add a comment