Firefox 53: Quantum Compositor, Compact Themes, CSS Masks

Post by TekMol » Wed, Apr 19, 2017, 8:30 PM UTC

kuschku wrote: post #52

hashhar wrote: post #44

Earlier 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.

Post by cpeterso » Wed, Apr 19, 2017, 8:36 PM UTC

yuhong wrote: post #43

callahad wrote: post #32

Earlier quoted context omitted.

We're still defaulting to 32-bit on systems where both are supported, but we hope to default to 64-bit around Firefox 55. We had to delay this due to issues with Flash, sandboxing, and Farmville 2: https://bugzil.la/1317995 The tracking bug for making 64-bit the default is https://bugzil.la/1340936

I dislike how the JIT don't comply with Windows x64 SEH requirements anyway. As a side note, I fixed NSS: https://bugzilla.mozilla.org/show_bug.cgi?id=1284375

Post by rvern » Wed, Apr 19, 2017, 8:38 PM UTC

dstaley wrote: post #59

yborg wrote: post #56

Earlier quoted context omitted.

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-chec…

Post by cpeterso » Wed, Apr 19, 2017, 8:41 PM UTC

reitanqild wrote: post #21

milescrabill wrote: post #11

Earlier quoted context omitted.

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 love it although now that I have a Mozilla employee here I should mention that: - it seems to be missing features when running with Tab Tree - the ux of Mozilla vertical tabs experiment is weird and IMO bad. And I rarely complain about UX. The problem is: the tab bar goes up on the side of the awesomebar and slides it back and forth as the tab panel expands and goes back. I have reported this but so far nobody seem…

Post by throwaway2048 » Wed, Apr 19, 2017, 8:42 PM UTC

kuschku wrote: post #52

hashhar wrote: post #44

Earlier 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.