Live data from Hacker News

Firefox 69.0 Released

mozilla.org

51–60 of 331 posts

Re: Firefox 69.0 Released

#51
post #2

For our users in the US or using the en-US browser, we are shipping a new “New Tab” page experience that connects you to the best of Pocket’s content. Uhmmm...

It _really_ bugs me that pocket isn't packaged as a pre-installed extension, that you can uninstall normally.

Re: Firefox 69.0 Released

#52

> macOS users on dual-graphics-card machines (like MacBook Pro) will switch back to the low-power GPU more aggressively, saving battery life. macOS user base can now consider FF as a viable browser alternative.

There are more macOS battery life improvements coming in Firefox 70 in around six weeks: https://news.ycombinator.com/item?id=20864255

For some measurements: https://bugzilla.mozilla.org/show_bug.cgi?id=1429522#c45

Re: Firefox 69.0 Released

#53
post #32

I have a bunch of Facebook domains in my hosts, but for some reason Firefox 69.0 gets DNS from somewhere else and goes right through. Weird. The other stuff in hosts resolves correctly.

Check that "network.trr.mode" is set to "0" in "about:config" to disable firefox using DNS over HTTPS (DoH). It was introduced in Firefox 62 I think.

You're better off setting it to "5". From https://wiki.mozilla.org/Trusted_Recursive_Resolver :

"Set `network.trr.mode` to 2 to make DNS Over HTTPS the browser's first choice but use regular DNS as a fallback (0 is "off by default", 1 lets Firefox pick whichever is faster, 3 for TRR only mode, 5 to explicitly turn it off)."

Re: Firefox 69.0 Released

#54
> The Block Autoplay feature is enhanced to give users the option to block any video that automatically starts playing, not just those that automatically play with sound.

Good. I know a news website that was on purpose disabling sound on videos to prevent that. So not only does it autoplay, you need to click to unmute anyway to actually hear it!

Why do news websites want to shove autoplaying videos on people's throats so much, what's wrong with playing at any time when you want?

And why do news websites even care about doing shoving it to the small percentage of people who actually bother to disable autoplay in their browser?

P.S. I already had autoplay for videos without sound disabled through about:config flags, but some videos managed to autoplay anyway. I wonder if they also fixed that issue, or simply made the about:config flag part of the settings dialog.

Re: Firefox 69.0 Released

#55

I've been using the Firefox 69 beta since it came out, and with auto-playing audio and video set to blocked, some sites still somehow manage to auto-start muted videos. Is this a bug I should report, or is there some exception that websites are taking advantage of (like starting the video via an event handler like onscroll)?

maybe it should be blocked by default, then one can "whitelist" domain.

My fingers are itching to ban some sites... such as cnn.com, dailymailco.uk

Re: Firefox 69.0 Released

#56
post #7

> Firefox no longer loads userChrome.css or userContent.css by default improving start-up performance. Users who wish to customize Firefox by using these files can set the toolkit.legacyUserProfileCustomizations.stylesheets preference to true to restore this ability. How much of a performance improvement does this make?

Holy shit, just why? It makes virtually no difference. Neither applying CSS (they already use a lot) nor loading a file take any time.

It has to have been showing up in profiles for them to bother, nobody would go out of their way to disable it otherwise. They added a pref to turn it back on and then disabled it instead of the easy thing (just removing it) which is some engineering effort plus testing effort to make sure the pref works right. Silly to do that for nothing.

Antivirus software does add a measurable delay to file operations sometimes, and each file is gonna be in its own sector so I could see them losing at least a few milliseconds there. Applying CSS does add overhead but the average user can't have that many rules in there so I suspect it's purely on the file i/o level.

Re: Firefox 69.0 Released

#57
> For our users on Windows 10, you’ll see performance and UI improvements:

> For our existing Windows 10 users, you can easily find and launch Firefox from a shortcut on the Win10 taskbar.

???

As opposed to before?!

Re: Firefox 69.0 Released

#58
post #5

It didn't make it to the developer notes, but Firefox 69 should be the first one to ship with unhandledrejection event on by default[0] - I'm so looking forward to being able to catch promises and do proper error handling on them in Firefox without having to jump through hoops [0] https://developer.mozilla.org/en-US/docs/Web/API/Window/unha...

But according to that page Safari still lacks support. Seems like that could cause enough issues alone to just skip using it.

Re: Firefox 69.0 Released

#60
post #30
post #7

> Firefox no longer loads userChrome.css or userContent.css by default improving start-up performance. Users who wish to customize Firefox by using these files can set the toolkit.legacyUserProfileCustomizations.stylesheets preference to true to restore this ability. How much of a performance improvement does this make?

Last time I tried, I just couldn’t get userContent.css to work at all. Maybe a user error, but I’d really like an easy way to set some default styles to override the inane Web 0.5 era defaults such as zero margins and unlimited-width paragraphs. Reading Good Old HTML (tm) pages sucks, and although there’s the reading mode, it tends to simply drop vital content it doesn’t happen to support…

I've used https://github.com/Aris-t2/CustomCSSforFx ever since ClassicThemeRestorer broke when they killed the old extensions. It seems to work fine for me.
Post reply on HN