rebelwebmaster

Meanwhile, Gnome still can't manage to display a desktop wallpaper when running at 4k resolution and 200% scaling.

https://gitlab.gnome.org/GNOME/gnome-shell/issues/1175

Kind of hard to get excited about perf improvements when relatively basic functionality manages to be broken for at least 7+ months and counting.

I wonder what that means for WebGL support on Mac. Though I guess it can run through an intermediate layer similar to ANGLE on Windows.

Native PiP is coming in Firefox 71 (already available for testing on Beta releases), though Windows-only at first. You can track macOS progress by following: https://bugzilla.mozilla.org/show_bug.cgi?id=1532675

There's a built-in extension blocklist which also gets updated remotely.

https://hg.mozilla.org/mozilla-central/file/tip/browser/app/...

It's almost like it was labeled as a Preview for a reason.

If it's not something sensitive, try filing a bug and attaching the PDF to it?

https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&c...

Skia is just one backend used for drawing pixels on the screen. It has nothing to do with deciding which pixels to draw in the first place (i.e. the vast majority of what web browsers do).

On 32-bit Windows, processes have maximum address space limitations which can be easily hit by web browsers. Having more content processes makes it less likely that any particular one will hit that limit. Note that content process OOM crashes are the #1 source of crash reports Firefox gets (and you can see plenty of other OOM crashes in that list further down too):

https://crash-stats.mozilla.com/topcrashers/?product=Firefox...

Could reduce out-of-memory crashes if fewer sites are sharing the same process.

Not saying the article is or isn't true, but how credible is Bloomberg as a news outlet these days after the SuperMicro story?

Who's even left from the leadership team around the time of Brendan Eich's departure? Mitchell Baker? Anybody else? Anyway, some say he was fired, some say he resigned. Are we ever going to know what really happened there? And finally, that happened 5 years ago (an eternity in tech time), how long does Mozilla need to be raked over the coals for it? At some point, do we ever move on?

My understanding from reading the bug reports is that the general cause of macOS performance issues is understood, but to do anything about it with the current architecture would require pulling developers off WebRender development instead. Instead, work is being done to make things better there for when that's ready to ship on Mac.

FWIW, the release notes for Firefox for Android call out scrolling performance improvements in 3 of the last 4 releases. Might be worth taking another look :)

The blog post linked from the release notes has some more information about AV1:

https://medium.com/mozilla-tech/mozilla-celebrates-release-o...

Firefox' devtools live in GitHub these days and can be patched without needing to build Firefox. I'm sure they'd welcome contributions from passionate developers.

https://github.com/devtools-html

Not a coincidence in my opinion that Mozilla's talking more about revenue diversification lately too.

Stylo has been shipping as part of desktop Firefox since the launch of version 57 last year. And with Firefox for Android since version 60.

roc left Mozilla back in 2016. https://robert.ocallahan.org/2016/03/leaving-mozilla.html

FYI, Containers in Firefox make life much better for having multiple Google accounts signed in at the same time.

Only when people decide to fight them. Sadly, many people un-aware of their dubious legality honor them even if they are in fact unenforceable.

Developer Edition builds are based on their current Beta version (Fx63 at this point) and this change just landed on Nightly, which is tracking Fx64.

The article mentions that GCC is still remaining a supported compiler and that there are automated builds in their CI to ensure that it stays working.

Fx63 (on Beta and Developer Edition) is on track to ship with clang-cl as the Windows compiler too.

I got the Win10 update yesterday and didn't have to accept any sort of license first.

In fact, Firefox currently can't build with the latest Visual Studio 2017 release due to internal compiler errors.

https://bugzilla.mozilla.org/show_bug.cgi?id=1458247

Probably not since Firefox for Android doesn't support multiprocess.

Weird. Maybe try filing a bug to see if someone who works on that feature has any other ideas.

https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&c...

Did screenshots somehow get disabled? In about:config, check the value of the extensions.screenshots.disabled pref.

On the right-hand side of the location bar, there's a Page actions menu (the 3 dots) which includes taking a screenshot.

The performance.now() change is due to ship to ESR users with the 52.6 release on January 23.