Firefox Quantum Isn’t Just “Copying” Chrome: It’s Much More Powerful
howtogeek.com
howtogeek.com
chrome://flags/, search for "autoplay", set to "Document user activation is required"
Anyone know of plans for Firefox and/or Chrome to implement a similar 1st-party content-blocking solutions for their respective browsers?
Opera for when running my laptop on battery Vivaldi when in the office.
Now, I've ditched Vivaldi and sticking with Opera & Firefox.
I suspect someone will create a Firefox Addon to auto-detect we running on batteries and throttle back on the performance settings.
#tabbrowser-tabs { visibility: collapse !important; }
Be warned that on Windows this kills the hidden "alt" menu bar and hides the close, expand, and minimize buttons. Works perfectly on linux though :P, I haven't tried on OSX.
FWIW, my only extensions are uBlock Origin and Tabs Outliner.
Also, Firefox start page is basically a glorified ads sponsored articles from their Pocket recommendation. Are people letting Mozilla getting away with this because it's owned by Mozilla? I honestly hate this practice. I don't want more ads.
Side Note: According to Mozilla's add-on site, Pentadactyl is only used by 289 users and appears to have been abandoned years ago, so it's doubtful that it's being worked on from either the extension side by an extension author or the WebExtensions side within Mozilla for features. Perhaps finding another extension (or commissioning one once keybindings are available in WebExtensions) would be in order.
I don't use Pentadactyl myself, I probably had in mind another extension (Vimperator).
>By then, the WebExtensions API will be even more powerful and enable additional extensions. >once keybindings are available in WebExtensions
They shouldn't have released anything until this extremely basic functionality is available to extensions. Otherwise it's just farce. Knowing Mozilla they will never implement this functionality because "nobody uses these extensions anymore" (because it's plain impossible to).
How am I supposed to use Firefox if I press Ctrl-W thousands of times per day? Even if I had an incredible accuracy of 99.99%, I'd still accidentally hit Ctrl-Q several times per day. Shouldn't the most basic functionality of a browser be "don't spontaneously close several times per day"?
They did. ESR was branched on schedule, the extension changes were well publicized, extensions were marked within the UI as having upcoming incompatibilities. And the breaking changes started before v57.
> I'd rather switch to Waterfox or Pale Moon or whatever.
Pale Moon is based on an even older and slower Firefox engine than Firefox ESR 52.x. Waterfox is planning on supporting legacy extensions, but whether they will set up the extensive manual review process that Mozilla has remains to be seen.
> I don't use Pentadactyl myself, I probably had in mind another extension (Vimperator).
Vimperator had I think 15,000 users at its peak, so it was likely that you were thinking of.
> They shouldn't have released anything until this extremely basic functionality is available to extensions. Otherwise it's just farce. Knowing Mozilla they will never implement this functionality because "nobody uses these extensions anymore" (because it's plain impossible to).
Firefox was bleeding users due to being slower and was having extreme difficulty implementing new features due to the ton of extra time to check if each feature altered existing extensions in any way sometimes adding months of implementation time.
> How am I supposed to use Firefox if I press Ctrl-W thousands of times per day? Even if I had an incredible accuracy of 99.99%, I'd still accidentally hit Ctrl-Q several times per day. Shouldn't the most basic functionality of a browser be "don't spontaneously close several times per day"?
Use Firefox ESR 52.x. It's stable and the same speed you're already accustomed to. By the time ESR is ready to move up to a later release in June, you can evaluate if Firefox 60/61 will suit your needs and support the types of extensions you want or going with an alternative implementation is a better idea.
Until then, you could also do some keybind changes at the OS level if you are so inclined and can find a suitable alternative that doesn't mess with your dev environment. You could also use ALT-HOME and use the standard built-in Firefox homepage.