UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36

Steps to reproduce the problem:
RMB drag gesture extensions don't work well on non-Windows platforms.

What is the expected behavior?

What went wrong?
There's currently pending feature request[1] for native gesture implementation. There's no need for this Chrome to mandate policy there though as this feature could be done well in an extension[2].

AFAIK most gesture extensions across all browsers use right mouse button (RMB) to draw gestures and users (including myself) are accustomed to it. As interactive web features become widespread, use of left mouse button drags on web pages has increased (rearranging table entries, ...), so use of RMB drags for gestures causes less conflicts as well.

RMB gestures don't have to conflict with context menu. For example, in simpleGestures[2], when user clicks RMB (without dragging), the event listener on contextmenu event returns true because no gesture was detected. This works, becuase on Windows, contextmenu is fired after mousedown and mouseup, so gesture detection happens before contextmenu.

The problem is that no such extension can work on non-Windows version of Chrome, because on Linux and Mac, the contextmenu event is fired right after mousedown and before mouseup. and there's no way to manually display the context menu from a content script. Such RMB gestures extension will have to either completely disable the context menu or, as simpleGestures[2] does it, allow to disable the gesture recognition with keyboard modifier (and let the contextmenu even through), but that defeats the purpose of mouse gestures.

PROPOSAL: Add boolean flag "Display context menu on RMB release" to chrome://flags applicable on non-Windows version of Chrome.

Several users already asked for context menu on RMB being default on non-Windows platform[3][4] but I agree that Chrome should behave as expected with no surprise on of each platform.

There's other proposal to add ability to display the context menu from content scripts[5]. While not officially rejected, it was proposed[6] to develop general-purpose mouse API instead referring to [1]. While the new API to achieve this is probably the way to go, it's too complex, no one is willing to even design it and as Chromium strives to be simple, it's probably not needed as functionality covered in [1] could be done in an extension.

This issue goes back to 2009 and all that is needed is to let users flip a boolean which I assume wouldn't be that intrusive change as Chrome already covers both cases. With this flag, users of non-Windows version of Chrome will be able to enjoy current gesture extensions and better solution could possibly develop in parallel.

[1] https://crbug.com/181
[2] https://github.com/RyutaKojima/simpleGestures
[3]  https://crbug.com/26465 
[4]  https://crbug.com/26666 
[5] https://crbug.com/28226
[6] https://crbug.com/28226#c21

Did this work before? N/A 

Chrome version: 51.0.2704.103  Channel: stable
OS Version: modern (2016)
Flash Version: