3 ms·

I ditched a load of addons for Firefox 57. Just embrace the change, find replacements, or move on and stop using them. It's hard, but I found I adapted quite qu

I ditched a load of addons for Firefox 57. Just embrace the change, find replacements, or move on and stop using them. It's hard, but I found I adapted quite quickly. For NoScript, even though it is now available, I switched to ublock in medium-mode since NS was delayed until a couple of weeks after 57 hit. Both ublock and NS now use the same Content-Security-Policy filtering approach (NoScript switched to CSP for the webextension release, ublock did it this way before) and so both now suffer from this bug that means noscript tags are not rendered/parsed at all https://github.com/gorhill/uBlock/issues/308 https://github.com/gorhill/uBlock/issues/308 - so I felt I may as well just use ublock. Full-on global-disallow NoScript with that bug makes many sites completely unusable since their graceful-degraded noscript blocks are not shown, and UI changes in the webextension release made it too fiddly to use IMO.

shostack 9y ago
Is there decent mouse gesture support for 57? That's one thing I'm not willing to budge on in terms of ditching old functionality from addons. Mouse gestures have become a way of life for me.
- CannisterFlux 9y ago
  Yes, me too. This was more of a pain than NoScript, but after trying a few I switched to "Foxy Gestures" and I'm mostly happy with it. It has right-button+move-in-a-pattern gestures, as well as "chorded" right/left clicks and wheel gestures. It does have 2 issues - 1st it does not work on special pages due to security restrictions. This means stuff like about:blank, when a page fails to load, preferences pages, and Mozilla's add-on site. There's nothing you can do about this regardless of the gestures add-on you use - life is worse due to security concerns, this is why we can't have nice things, etc. And 2nd on Linux (maybe Mac too) Foxy Gestures did not work at all by default since the right-click menu triggers on mouse down, not mouse up. That stopped the gesture in their tracks. The FoxyGestures developer mitigated this problem by making right-menu take 2 clicks to trigger as an option enabled by default on Linux, but that can be annoying as now the regular right-click menu doesn't appear when you expect. Fortunately a patch is in Firefox for a future version that adds the option "ui.context_menus.after_mouseup", which makes the right-click menu work like on Windows. Also, a bonus, on Arch Linux the packager backported that preference to Firefox 57, so nice of them, which made everything work almost as well as in the pre-57 days.

shostack 9y ago

Is there decent mouse gesture support for 57? That's one thing I'm not willing to budge on in terms of ditching old functionality from addons. Mouse gestures have become a way of life for me.

CannisterFlux 9y ago
Yes, me too. This was more of a pain than NoScript, but after trying a few I switched to "Foxy Gestures" and I'm mostly happy with it. It has right-button+move-in-a-pattern gestures, as well as "chorded" right/left clicks and wheel gestures. It does have 2 issues - 1st it does not work on special pages due to security restrictions. This means stuff like about:blank, when a page fails to load, preferences pages, and Mozilla's add-on site. There's nothing you can do about this regardless of the gestures add-on you use - life is worse due to security concerns, this is why we can't have nice things, etc. And 2nd on Linux (maybe Mac too) Foxy Gestures did not work at all by default since the right-click menu triggers on mouse down, not mouse up. That stopped the gesture in their tracks. The FoxyGestures developer mitigated this problem by making right-menu take 2 clicks to trigger as an option enabled by default on Linux, but that can be annoying as now the regular right-click menu doesn't appear when you expect. Fortunately a patch is in Firefox for a future version that adds the option "ui.context_menus.after_mouseup", which makes the right-click menu work like on Windows. Also, a bonus, on Arch Linux the packager backported that preference to Firefox 57, so nice of them, which made everything work almost as well as in the pre-57 days.