Gestures not working with privacy.resistFingerprinting = true

[ksolheim]

Gesturefy 1.2.1 - Firefox 60.0b6 (64-bit) - Windows 7

When attempting to perform a gesture (on any page) it snaps to the top left corner and refuses to move any further.
I've tried resetting the Gesturefy config and disabling all other addons, none made any difference.

Reverting to 1.2.0 fixes the issues.

[Robbendebiene]

Thanks for the info, unfortunately it's working for me fine on Firefox 60. Does this also happen if you make a clean install of Gesturefy 1.2.1?

[ksolheim]

I've tried the following:

1. Remove Gesturefy 1.2.1
2. Restart Firefox.
3. Install Gesturefy 1.2.

This did not help.

However I tried 'Refresh Firefox...' and afterwards 1.2.1 installs and works as intended.

[Robbendebiene]

Thanks for the info.
Seems like a Firefox related problem. Hopefully this was a unique case.

[Robbendebiene]

The problem seems to be the about:config setting: privacy.resistFingerprinting

[je-nix]

I can confirm this issue (Arch Linux, Xorg, i3 WM, Firefox 59.0.1) and that privacy.resistFingerprinting causes it. When I set it to false, Gesturefy 1.2.1 works as intended. If set to true, all gestures start at the top left corner of the window, making it impossible (or at least very hard) to draw any commands. After reverting back to 1.2.0 all is well again.
Since I want to keep this setting enabled, I hope that you will find a solution for this issue. Thanks.

[Robbendebiene]

To give a little update on this topic: I asked the Mozilla community about their opinion on this problem and they kindly agreed that addons should not be affected by this setting. They plan to change the behaviour, which will fix the encountered problems. (more information here)

[ldgbc]

Those Mozilla guy still haven't fixed this?!

Did they fixed it?

Saw this:
BMO Automation

Updated • 24 days ago
Product: Toolkit → WebExtensions
Statuses changed RESOLVED (18161), FIXED (0), VERIFIED (0), INVALID (0)

[Robbendebiene]

Did they fixed it?

@ldgbc No, it's still not assigned to a developer.

[sbstn87]

Any updates on the issue?

BTW, I am still using version 1.2.0 of Gesturefy - that version works when using privacy.resistFingerprinting is set to True. What has changed in 1.2.1 and later version that prevents it from working correctly?

[xuzhen]

Why not use clientX/clientY instead of screenX/screenY like Foxy Gestures?

[Symbai]

There is also Mouse Gesture Events addon which works when privacy.resistFingerprinting=true it also works if the site you are visiting has restricted (javascript) access. It seems to use a completely different approach than Gesturefy and Foxy Gesture addon. It's source code is https://iloe.ru/gestures/source-code/ if someone who is able to read it wants to take a look. Maybe its approach can be adopted?

[Robbendebiene]

The fix for this problem is already coded, but it will be released together with version 3.

it also works if the site you are visiting has restricted (javascript) access.

Can you further explain what you mean by that?

[Symbai]

@Robbendebiene Using Gesturefy or Foxy Gesture I often have the problem that mouse gestures are no longer recognized for certain tabs. Previously I was using Mouse Gesture Events and it always worked (except of Firefox pages (addons, settings etc) but that's normal).

I was reading these addons inject code into the site I am visiting. So my thought was that because I am using noscript and other addons, the injected code will not work then.

[Robbendebiene]

@Symbai I can not explain why Gesturefy stops working for you, but all gesture add-ons have to inject code into the website you visit (including Mouse Gesture Events). I also doubt that Noscript is able to block code injected by add-ons. However there might be other extensions related to mouse events that lead to problems with Gesturefy.

If your problem occurs repeatedly and you can detect some sort of pattern feel free to open an issue for that.