Hacker Read top | best | new | newcomments | leaders | about | bookmarklet login

I have webrender testing enabled and three days ago I opened Firefox Nightly and the UI was completely wrecked due some unexpected WebRender bug that was fixed after updating. So I’m glad they’re testing it on expert users first :)

EDIT: Nope, I’m not one of the default-on “safe” configurations.



sort by: page size:

> WebRender is already turned on by default for many users in Firefox Nightly…

Are you using Nightly?


That's really cool. Big thanks to the team behind this!

The biggest feature for me was that it can run alongside the normal version of Firefox so I could tinker with it without disrupting day-to-day workflow.

Not like it's a big deal or anything, but it still shows a warning when you enter about:config even though it's targeted at devs :)


Seems to work nicely in Firefox 50 release (no nightly required) once the config is set.

Really happy about the way this is progressing.


I also use Firefox Nightly. But was rudely surprised to notice that settings were getting reset after nightly upgrades. This is really poor decision by Firefox. If they expect early adopters to use and give feedback, then they should be friendly to them.

Firefox 70 is currently available in the beta and developer edition channels.

This feature requires WebRender to be enabled, according to the release notes:

https://www.mozilla.org/en-US/firefox/70.0beta/releasenotes

WebRender is automatically enabled for certain browser configurations:

https://wiki.mozilla.org/Platform/GFX/WebRender_Where

Anyone without these configurations can force WebRender on by setting gfx.webrender.all to "true" in about:config.


Mozilla pushed a hotfix yesterday but it only worked on certain builds of Firefox, and only for users which had the user studies setting activated. Today's update should be a more permanent fix.

Thanks for restoring order to my world view. I always face Firefox updates these days with trepidation about what fundamental interface functionality they're going to turn from perfectly adequate to shit this time. The present update seemed to break the pattern, but apparently things are going according to expectations after all.

And so far it's a bug that has an off-switch. Best kind. Much obliged for the documentation.


> Firefox develop a feature working on Mac OS only.

Looks to me like this is an experimental feature in Nightly. If it's highly system-dependent I can't blame them for testing the feedback as early as possible, before other systems are supported.

Question for Mozilla people here, if anyone sees it - is there a plan to bring this feature across all systems in time for regular Firefox release?


You can use Firefox nightly and enable any that you want.

I'd rather use the version of Firefox that doesn't crash more frequently, but that's the trade-off I gotta make at the moment.


This only applies to executables I think, as I've never seen the warning on Firefox Nightly.

Oh wow, putting Firefox in private browsing mode did not defeat it. That'll probably get fixed pretty quickly, I hope.

Same. I run Firefox Nightly with everything under "Nightly Data Collection and Use" checked.

I enabled it for the bugfix and it made some additional changes to the config that weren't related to the bug fix and not mentioned on about:studies. Changed the behavior of the browser.

Very strange and unsettling.


> you can in firefox settings

Obviously a remnant from the Netscape codebase. They will fix it.


I've always left "Allow Firefox to send technical and interaction data to Mozilla" and "Allow Firefox to send crash reports to Mozilla" enabled, and I've been using Firefox since it was Phoenix (beta) in the early oughts.

I just like to make sure they get the info they need to improve it and also, advocate in that way for the features within the browser that I use- so they don't remove them. After this study add-on, I disabled all of those settings.

I'm not moving to Chrome (and I never did all these years, FF has features that Chrome never will like toolbar RSS feed support), but now I'm probably withholding legitimately helpful information from Mozilla. I'm willing to do that because I don't feel like they can be trusted right now.


FWIW, it was already enabled for me in Nightly on MacOS - 83.0a1 (2020-09-25) (64-bit)

Thanks for all of your hard work. Firefox forever!


Ive been using it since Firefox 58, where they fixed a bug that broke cookie-whitelisting.

Ive been pretty happy. The only website where it really is a problem is Playstation Network, but I have an addon that disables FPI when I really need to temporarily.


I think it really should not prompt to be the default browser when you launch it (and maybe never show this prompt like Chrome Canary).

A colleague had a weird race condition (I guess) with this prompt + the "how-to" overlays and Firefox Developer Edition stopped responding to clicks 3 seconds after launching it…

Kudos for using a different profile than the classic Firefox/Nightly :)


Um, what? I have a shadow DOM experiment from 2016 that's worked on Firefox since then... (an over-engineered webcomic tracker, I use it almost every day)

Is this about a better API or something?

Edit: Ohh, I must have enabled it in about:config manually back then. It's existed since at least Jan 2015 [0], but was disabled by default until this just now in Nightly.

[0] https://www.designedbyaturtle.co.uk/2015/how-to-enable-web-c...

next

Legal | privacy