Live data from Hacker News

Firefox 53: Quantum Compositor, Compact Themes, CSS Masks

hacks.mozilla.org

91–100 of 108 posts

Re: Firefox 53: Quantum Compositor, Compact Themes, CSS Masks

#91

Earlier quoted context omitted.

My Pale Moon (Linux) clocks in at around 200Mb less than latest Firefox. It's faster, too. And runs the addons I want it to run. Not going back.

How well is Pale Moon patching disclosed Firefox vulnerabilities?

Probably not as well as a whole, large, dedicated corporation-like setup a la Mozilla.

On the other hand, it's not moving absurdly fast and breaking things as a matter of policy like recent Firefox is.

With sensible browsing habits and a very conservative use of js, I'm confident enough, day to day.

Re: Firefox 53: Quantum Compositor, Compact Themes, CSS Masks

#92
post #77
post #65

Earlier quoted context omitted.

Electrolysis has been enabled by default since Firefox 48. Source: https://wiki.mozilla.org/Electrolysis#Schedule .

> As of Firefox 54+ (early 2017), our Multi-Content process model is currently being tested on Nightly (4 processes). Four content processes will be enabled on 54 Aurora and if stable enough, we will begin to roll it out in Firefox 54 Beta experiments. This seems to be the case because I downloaded Firefox 53 for the first time on my new MacBook Pro and e10s wasn't enabled. I had to go to about:config and enable it m…

Firefox 52 shipped with e10s enabled by default for all users except those who are on Windows XP, have a windows machine with a touchscreen, or have extensions that are not compatible with e10s. It uses one browser UI process and one web content process.

Firefox 54 has e10s-multi, with multiple web content processes.

If you go to about:support in your Firefox 53, the "Multiprocess Windows" item in the first section ("Application Basics") should tell you why e10s is disabled for you, if it's disabled.

Re: Firefox 53: Quantum Compositor, Compact Themes, CSS Masks

#93

Earlier quoted context omitted.

My Pale Moon (Linux) clocks in at around 200Mb less than latest Firefox. It's faster, too. And runs the addons I want it to run. Not going back.

How well is Pale Moon patching disclosed Firefox vulnerabilities?

I expect very well. The devs are VERY security focused if you spend time reading their changelogs.

Re: Firefox 53: Quantum Compositor, Compact Themes, CSS Masks

#94

And, as always, I just added Firefox 53 to Browserling. You can try this new version at this URL without installing or updating it: https://www.browserling.com/firefox/53/news.ycombinator.com I've a bunch of VMs available for free testing. If there are too many people wanting to try it, then you'll have to wait in a queue for a few minutes.

In the same vein, Windows users can grab the portable version of Firefox 53 and use it without needing to install it, without needing admin rights, and without interfering with a different version installed within Windows:

https://portableapps.com/apps/internet/firefox_portable

In addition to the stable channel, you can grab beta, dev, nightly, and esr and automatically update them within the PortableApps.com Platform. We also have all old major versions of it available on our SourceForge project. They're all free and fully open source.

Re: Firefox 53: Quantum Compositor, Compact Themes, CSS Masks

#95
post #77

Earlier quoted context omitted.

> As of Firefox 54+ (early 2017), our Multi-Content process model is currently being tested on Nightly (4 processes). Four content processes will be enabled on 54 Aurora and if stable enough, we will begin to roll it out in Firefox 54 Beta experiments. This seems to be the case because I downloaded Firefox 53 for the first time on my new MacBook Pro and e10s wasn't enabled. I had to go to about:config and enable it m…

Firefox 52 shipped with e10s enabled by default for all users except those who are on Windows XP, have a windows machine with a touchscreen, or have extensions that are not compatible with e10s. It uses one browser UI process and one web content process. Firefox 54 has e10s-multi, with multiple web content processes. If you go to about:support in your Firefox 53, the "Multiprocess Windows" item in the first section (…

The only thing it says for me is "0/1 (Disabled)". [0]

Edit: Ah, so this is weird. It looks like e10s isn't enabled when you first run Firefox. You need to quit, and then relaunch. On the second launch e10s is then enabled. This explains why I thought it was disabled by default (since it was my first time running Firefox on this machine).

[0] https://gist.github.com/dstaley/b17ce52947cf520ca793d545daee...

Re: Firefox 53: Quantum Compositor, Compact Themes, CSS Masks

#96
post #95

Earlier quoted context omitted.

Firefox 52 shipped with e10s enabled by default for all users except those who are on Windows XP, have a windows machine with a touchscreen, or have extensions that are not compatible with e10s. It uses one browser UI process and one web content process. Firefox 54 has e10s-multi, with multiple web content processes. If you go to about:support in your Firefox 53, the "Multiprocess Windows" item in the first section (…

The only thing it says for me is "0/1 (Disabled)". [0] Edit: Ah, so this is weird. It looks like e10s isn't enabled when you first run Firefox. You need to quit, and then relaunch. On the second launch e10s is then enabled. This explains why I thought it was disabled by default (since it was my first time running Firefox on this machine). [0] https://gist.github.com/dstaley/b17ce52947cf520ca793d545daee...

"Disabled" means there was an explicit pref set to disable it.

I can't tell from over here what preferences you changed and in what order and when. You said "I had to go to about:config and enable it manually"... did you restart after that? e10s pref changes require a restart to take effect. What was the state of the preferences before you did that, if you remember?

In any case, glad to hear it's working for you now.

Re: Firefox 53: Quantum Compositor, Compact Themes, CSS Masks

#97
post #60

Earlier quoted context omitted.

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.

Do people actually make web pages that try to look native to the OS they're loaded on? That is a lot of effort to reimplement GUI toolkits and I can't think of anything I've seen that does it.

I'd say the real way to look native in firefox involves XUL, even if it is getting removed.

Re: Firefox 53: Quantum Compositor, Compact Themes, CSS Masks

#98
post #72

Earlier quoted context omitted.

Quantum Compositor is just a separate process for GPU stuff. It isn't ported from Servo.

It's the same name as the Servo porting project. I could see that creating the separate process is a first step and involves no Servo code as of yet, but how do you know either way?

mccr8 is a Mozilla engineer.

Re: Firefox 53: Quantum Compositor, Compact Themes, CSS Masks

#99
post #72

Earlier quoted context omitted.

Quantum Compositor is just a separate process for GPU stuff. It isn't ported from Servo.

It's literally ported from Servo. > The goal of the Quantum Render project is to take the WebRender compositor in Servo and embed it in Firefox https://wiki.mozilla.org/Platform/GFX/Quantum_Render

That's Quantum Render, not Quantum Compositor.

Re: Firefox 53: Quantum Compositor, Compact Themes, CSS Masks

#100
post #80

Earlier quoted context omitted.

If you watch a lot of Youtube, force the video to MP4 so your graphics card can decode it in hardware. Youtube defaults to VP9 but gfx cards rarely support that codec. Google's wasting a lot of battery life by pushing VP9 onto everyone.

Hardware video decoding does not work in linux period. It doesn't matter whether you play an mp4 or vp9 video.

Not sure what you mean by that.

It's true that Chrome/Chromium don't support it. [0]

Linux itself certainly supports it [1], and at least Mozilla have some progress towards it happening [2][3][4], if slow progress.

However, we used to have hardware video decoding via gstreamer and VLC within Firefox as plugins, using VAAPI and NPAPI, so it's still possible to get working today.

[0] https://bugs.chromium.org/p/chromium/issues/detail?id=463440

[1] https://wiki.archlinux.org/index.php/Hardware_video_accelera...

[2] https://bugzilla.mozilla.org/show_bug.cgi?id=563206

[3] https://bugzilla.mozilla.org/show_bug.cgi?id=1210729

[4] https://bugzilla.mozilla.org/show_bug.cgi?id=1210726

Post reply on HN