To reproduce, take a DIV element and add the following to it:
for left-clicks:
onclick="console.log([event.altKey, event.shiftKey, event.ctrlKey])"
and for right-clicks:
oncontextmenu="console.log([event.altKey, event.shiftKey, event.ctrlKey])"
Using left-clicks the "modifier key booleans" still work fine with FireGestures, but if you do CTRL + right-click for example, the above will show [false, false, false] in the console.
If you disable FireGestures-AddOn and restart the browser, CTRL + right-click will log [false, false, true] to the console. Whatever modifier key (or combination of them) you hold while right-clicking, the corresponding booleans of the event will always be false (if FireGestures is activated).
I use to do CTRL + right-click in a web application in order to force the browsers context-menu instead of the web applications js/html-context-menu.
To reproduce, take a DIV element and add the following to it: for left-clicks: onclick="console.log([event.altKey, event.shiftKey, event.ctrlKey])"
and for right-clicks: oncontextmenu="console.log([event.altKey, event.shiftKey, event.ctrlKey])"
Using left-clicks the "modifier key booleans" still work fine with FireGestures, but if you do CTRL + right-click for example, the above will show [false, false, false] in the console. If you disable FireGestures-AddOn and restart the browser, CTRL + right-click will log [false, false, true] to the console. Whatever modifier key (or combination of them) you hold while right-clicking, the corresponding booleans of the event will always be false (if FireGestures is activated).
I use to do CTRL + right-click in a web application in order to force the browsers context-menu instead of the web applications js/html-context-menu.