Earlier quoted context omitted.
This might be too much for you, but if it's looking too tight, note that there's also a Density menu at the bottom in the customisation screen that lets you widen the interface (including, presumably, the bars).
I have my density set to compact, changing it affects the vertical space of everything except the bookmarks and menu bars. They remain incredibly tight.
Firefox 57.0 Released
771–780 of 836 posts
Re: Firefox 57.0 Released
#772Earlier quoted context omitted.
Depends on your needs. If it's mostly the shortcuts, Vimium works pretty well (at least for me). If you want the full-blown UI customisation, then I'm afraid extensions are not allowed that anymore due to the associated security risks.
Has Vimium been updated to work under the new extension system?
VimFx hasn't, but Vimium has replaced it for me.
Re: Firefox 57.0 Released
#773Earlier quoted context omitted.
Depends on your needs. If it's mostly the shortcuts, Vimium works pretty well (at least for me). If you want the full-blown UI customisation, then I'm afraid extensions are not allowed that anymore due to the associated security risks.
Vent mode on: That is pathetic. More paternalistic nannying of the user, making their life actively worse in favor of closing off a very limited security hole. If that’s the mindset, wouldn’t it be even safer to not have a browser at all?
I mean, obviously there's pros and cons, but it's a damned if you do, damned if you don't situation.
Re: Firefox 57.0 Released
#774Earlier quoted context omitted.
Depends on your needs. If it's mostly the shortcuts, Vimium works pretty well (at least for me). If you want the full-blown UI customisation, then I'm afraid extensions are not allowed that anymore due to the associated security risks.
> If you want the full-blown UI customisation, then I'm afraid extensions are not allowed that anymore due to the associated security risks. That's total BS. It's my software running on my computer. I get to decide what I consider a security risk, not Mozilla.
As I said elsewhere, it is frustrating as well. But it's not like there aren't upsides to it as well, that just might not apply to us.
Re: Firefox 57.0 Released
#775Re: Firefox 57.0 Released
#776Firefox Quantum feels very fast, but addon support is disappointing :( + uBlock Origin - Self-Destructing Cookies - YesScript - Video DownloadHelper - Save Session
Edit: Forgot to mention but if you check the add-ons site, you should be able to find an updated extension for Video DownloadHelper.
Re: Firefox 57.0 Released
#777Re: Firefox 57.0 Released
#778I just updated - WOW! What an improvement! Compared startup time and scrolling around some over-monetized sites; Behaves just as well as Chrome. Time for a switch again, I've missed FireFox since I started having Chrome as my default browser back in ~2011
Now Google just needs to test their apps like Drive on it... I stopped using Firefox partly because they were so buggy on it.
Re: Firefox 57.0 Released
#779Earlier quoted context omitted.
Firefox is pretty similar looking as Chrome now. I liked FF before cause it looked different, now everyone just copies Chrome look.
Does it? As a matter of fact, it's much more similar to MS Edge. With dark theme it's super close in terms of look. Rectangular, beefy tabs.
https://winaero.com/blog/wp-content/uploads/2017/11/firefox-...
Re: Firefox 57.0 Released
#780Earlier quoted context omitted.
> Note that the webextension APIs are still under active development. In which case, switching to webextension support exclusively is premature at this point, don't you think? It would have been better to wait until the API was robust enough to allow 99.99% of legacy extensions to be ported.
Unfortunately, this would have meant no Firefox Quantum. As a Firefox dev (I'm still working at Mozilla, although not much on Firefox atm), I have seen many, many occurrences in which I couldn't optimize codepaths, or even in some case fix bugs, because the old extension mechanism made it impossible. Consider the necessary steps: 1. realize that an internal API is broken; 2. come up with a new non-broken API; 3. port…