News for hackers. Stuff that matters.

A comment on Firefox 70. Parent comment

Re:Firefox 70 by lordnacho on Tuesday October 22, 2019 @10:56AM (#21324301)
I just tried this. Interestingly I'd left it on v68 and it cooked my MBP, fans all on max immediately. When I updated to 70 it seems to work perfectly. CPU temp in the 40s. Gonna leave it on in the background and see if it suddenly spikes.
[ Parent | on HN ]
Re:Firefox 70 by chenster on Tuesday October 22, 2019 @11:30AM (#21324769)
The same here. Have you tried with FF add-ons that normally are the culprit for CPU hogging?
[ Parent | on HN ]
Re:Firefox 70 by lordnacho on Tuesday October 22, 2019 @12:17PM (#21325428)
Yeah, they're all on. Seems to be fine thus far, and there's an article about what they actually did to fix it, so I'm ready to say it's fixed.

Only minor gripe is userChrome.css seems to not be used now.

[ Parent | on HN ]
Re:Firefox 70 by sharps1 on Tuesday October 22, 2019 @12:35PM (#21325652)
You need to enable it in about:config

Set this option to true: toolkit.legacyUserProfileCustomizations.stylesheets

[ Parent | on HN ]
Re:Firefox 70 by Karunamon on Tuesday October 22, 2019 @12:59PM (#21325976)
That's a slightly worrying precedent, they're calling the way to diaable certain bits of obnoxiousness (the header bar in Tree Style Tabs comes to mind) "legacy", which is usually a precursor to removal.

Is there a new method available/forthcoming, or is this more control planned to be wrenched out of user's hands?

[ Parent | on HN ]
Re:Firefox 70 by lordnacho on Tuesday October 22, 2019 @12:54PM (#21325897)
Was set to true already.
[ Parent | on HN ]
Re:Firefox 70 by carey on Wednesday October 23, 2019 @03:12AM (#21331957)
Was it referring to browser.xul? There’s no XUL left, so you might need to change that to browser.xhtml.
[ Parent | on HN ]