Firefox 69.0 Released

Post by jahlove » Tue, Sep 03, 2019, 7:38 PM UTC

slater wrote: post #206

Aardwolf wrote: post #82

> 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. With all due respect, if you have to call it an "experience" you know it's something nobody asked for :p

I just wish they'd once and for all drop Pocket. At what point do they understand that it's a failed experiment if they constantly have to re-enable and/or "ship" an "experience"?

Post by CommieBobDole » Tue, Sep 03, 2019, 7:40 PM UTC

acdha wrote: post #163

Aardwolf wrote: post #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 throat…

> 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? There was a bubble awhile back when advertisers were being told that video had better metrics, and all of the news sites jumped on higher-paying ads. That seems to have tapered off as advertisers noticed poor returns and learned that Facebook had been massively misrepresenting the…

Post by jahlove » Tue, Sep 03, 2019, 7:46 PM UTC

xtreak29 wrote: post #37

kuu wrote: 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...

Curious over what it does. This seems to be the meta bug tracking this : https://bugzilla.mozilla.org/show_bug.cgi?id=1535711 . There are lot of linked issues and there is no clear description over this behavior. Can someone add in a link?

Post by dewaine » Tue, Sep 03, 2019, 7:54 PM UTC

Post by jahlove » Tue, Sep 03, 2019, 7:56 PM UTC

StavrosK wrote: post #171

bzbarsky wrote: post #149

Earlier quoted context omitted.

The technical answer to the question you asked is "10-20ms, if you're not on an SSD". That's not great, actually, if you're trying to shave tens of milliseconds at a time off startup performance. For what it's worth, this change happened because people were seeing the stat() call involved in startup profiles, taking sufficient time that it seemed worthwhile to avoid it if possible, as far as I can tell.

Are many users on HDDs these days? Weird that it would take this long, although I guess it's niche enough that you'd want to save those 20 ms for something used by a tiny fraction of users.