You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently mouse button modifiers, introduced in #4866, are left, middle, right for $event.button values 0, 1, 2 correspondingly. But that is only correct for the "default" right-handed layout. In the left-handed mode (when the buttons are switched in the OS) the right button has 0 value and the left button - 2. Besides, also some right-handed users may reverse or remap the mouse buttons. And working with code with these names for mouse buttons may lead to confusion and bugs among developers not familiar with the "default" right-handed mode being the target for these modifiers.
What does the proposed API look like?
Keep left and right as deprecated and add main and secondary as their aliases.
The text was updated successfully, but these errors were encountered:
What problem does this feature solve?
Currently mouse button modifiers, introduced in #4866, are
left
,middle
,right
for$event.button
values0
,1
,2
correspondingly. But that is only correct for the "default" right-handed layout. In the left-handed mode (when the buttons are switched in the OS) the right button has0
value and the left button -2
. Besides, also some right-handed users may reverse or remap the mouse buttons. And working with code with these names for mouse buttons may lead to confusion and bugs among developers not familiar with the "default" right-handed mode being the target for these modifiers.What does the proposed API look like?
Keep
left
andright
as deprecated and addmain
andsecondary
as their aliases.The text was updated successfully, but these errors were encountered: