I love the compact themes - it always unreasonably annoyed me how much vertical space the browser chrome "wastes"!
I love it too, excellent feature!
Firefox 53: Quantum Compositor, Compact Themes, CSS Masks
51–60 of 108 posts
Re: Firefox 53: Quantum Compositor, Compact Themes, CSS Masks
#52Still no hardware accelerated video for Linux :( Everytime Firefox releases something I am reminded of this: https://xkcd.com/619/
You can easily force enable it. But the stability varies wildly with hardware. My iGPU works good, my NVIDIA 920m works good but the old AMD 5750HD causes crashes. Go to about:config and set: layers.acceleration.force-enabled to true. BUG REPORT: https://bugzilla.mozilla.org/show_bug.cgi?id=594876
Nope, that's hardware accelerated layers and compositing.
Video is always decoded on CPU on Linux. Always. Eating, at 4K, around 5-10% on an i7-6700.
On a smaller laptop, this can eat an entire core, and make the browser close to unusable.
Re: Firefox 53: Quantum Compositor, Compact Themes, CSS Masks
#53Ha, what unexpected Rickroll! :D
Oh no! That actually should've worked as described (not auto-playing until you switch tabs), but it looks like auto-play suppression is in 54, not 53. Sorry :( https://bugzil.la/1308154
Re: Firefox 53: Quantum Compositor, Compact Themes, CSS Masks
#54I switched to Chrome in 2016 because I needed to easily switch between multiple profiles. With Firefox I have to launch with a command line switch. :(
You should check out Container tabs in Firefox: https://wiki.mozilla.org/Security/Contextual_Identity_Projec... . It's like per-tab profiles, no need for multiple copies of the browser, etc. Totally changed the way I deal with sites I need multiple accounts for (like AWS). You can use Containers in Nightly or via the Containers Testpilot experiment here: https://testpilot.firefox.com/ . disclaimer: I work for Mozilla
As you're already here, when can we expect Firefox to...
(a) read QT_SCREEN_SCALE_FACTORS to do per-screen dpi scaling on Linux? Currently there's an old-style extension to read this, and scale the browser accordingly, but with WebExtension only, I'd be stuck with a browser that's always the wrong scale.
(b) support hardware video decoding on Linux? Currently I use a plugin to force Firefox to use VLC to handle HTML5 video, wherever possible, so I can get fluent video - with WebExtension, this won't be possible, and CPU-decoding of HTML5 video eats over 5-10% of CPU even on an i7-6700 with a 4K video. On laptops, it's almost unusable.
(c) How long do you expect it to take until we can customize the entire browser chrome with HTML, CSS and JS again? XUL will be gone, but with Browser.html, and competing browsers such as Vivaldi, these things are possible easily. As we're already on that topic...
(d) as you don't seem to be willing to implement Tab Previews in the browser itself, when can we expect a WebExtension API to do so ourselves? In old-style extensions it is possible, but this breaks with WebExtension.
Re: Firefox 53: Quantum Compositor, Compact Themes, CSS Masks
#55Whenever a new Firefox release drops, my favorite thing to do is to see if this (now ten-year-old) bug [0] is finally fixed. Spoiler: it isn't. This bug (and many others similar to it) are one of the main reasons I dislike using Firefox. It just feels out of place on macOS. I'm fine with non-native UI elements as long as they're not elements as fundamental as the select dropdown and the right-click menu. Edit: Turns…
Re: Firefox 53: Quantum Compositor, Compact Themes, CSS Masks
#56Whenever a new Firefox release drops, my favorite thing to do is to see if this (now ten-year-old) bug [0] is finally fixed. Spoiler: it isn't. This bug (and many others similar to it) are one of the main reasons I dislike using Firefox. It just feels out of place on macOS. I'm fine with non-native UI elements as long as they're not elements as fundamental as the select dropdown and the right-click menu. Edit: Turns…
My favorite thing is coming to the HN threads to read the "tried it out to see if is fixed (meaning works the way I want it to work) but it's not, therefore the entire project A SHIT" posts.
The fact that this one then acknowledges that the bug is actually fixed if you use the browser in the recommended mode gives it extra points.
Re: Firefox 53: Quantum Compositor, Compact Themes, CSS Masks
#57I switched to Chrome in 2016 because I needed to easily switch between multiple profiles. With Firefox I have to launch with a command line switch. :(
You should check out Container tabs in Firefox: https://wiki.mozilla.org/Security/Contextual_Identity_Projec... . It's like per-tab profiles, no need for multiple copies of the browser, etc. Totally changed the way I deal with sites I need multiple accounts for (like AWS). You can use Containers in Nightly or via the Containers Testpilot experiment here: https://testpilot.firefox.com/ . disclaimer: I work for Mozilla
i have so been needing this! no more opening new windows, private windows, and new browsers with private windows to test multiple user scenarios. [thumbsup emoji]
Re: Firefox 53: Quantum Compositor, Compact Themes, CSS Masks
#58Earlier quoted context omitted.
You can easily force enable it. But the stability varies wildly with hardware. My iGPU works good, my NVIDIA 920m works good but the old AMD 5750HD causes crashes. Go to about:config and set: layers.acceleration.force-enabled to true. BUG REPORT: https://bugzilla.mozilla.org/show_bug.cgi?id=594876
Nope, that's hardware accelerated layers and compositing. Video is always decoded on CPU on Linux. Always. Eating, at 4K, around 5-10% on an i7-6700. On a smaller laptop, this can eat an entire core, and make the browser close to unusable.
Reminds me of https://stackoverflow.com/questions/23289157/how-to-use-hard....
The entire Linux graphics stack is fragmented and makes things worse for both users and developers.
Re: Firefox 53: Quantum Compositor, Compact Themes, CSS Masks
#59Whenever a new Firefox release drops, my favorite thing to do is to see if this (now ten-year-old) bug [0] is finally fixed. Spoiler: it isn't. This bug (and many others similar to it) are one of the main reasons I dislike using Firefox. It just feels out of place on macOS. I'm fine with non-native UI elements as long as they're not elements as fundamental as the select dropdown and the right-click menu. Edit: Turns…
My favorite thing is coming to the HN threads to read the "tried it out to see if is fixed (meaning works the way I want it to work) but it's not, therefore the entire project A SHIT" posts. The fact that this one then acknowledges that the bug is actually fixed if you use the browser in the recommended mode gives it extra points.
Electrolysis isn't enabled by default, so I don't think it qualifies as "the recommended mode".
Furthermore, I never said "the entire project is shit". Firefox is a great piece of software, but I don't use it personally because of the issue I mentioned, among other issues in the same category (like the right-click menu looking different compared to other right-click menus, or not integrating with the macOS spell-check system).
Re: Firefox 53: Quantum Compositor, Compact Themes, CSS Masks
#60Whenever a new Firefox release drops, my favorite thing to do is to see if this (now ten-year-old) bug [0] is finally fixed. Spoiler: it isn't. This bug (and many others similar to it) are one of the main reasons I dislike using Firefox. It just feels out of place on macOS. I'm fine with non-native UI elements as long as they're not elements as fundamental as the select dropdown and the right-click menu. Edit: Turns…
Your standard of quality is whether a web page looks like it's not a web page?
The standard of quality is if you can build applications that behave as if they were native with a browser.
Considering stuff like Electron and co, that's not an unusual request.