Firefox 69.0 Released
81–90 of 331 posts
Re: Firefox 69.0 Released
#82With all due respect, if you have to call it an "experience" you know it's something nobody asked for :p
Re: Firefox 69.0 Released
#83> 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
Re: Firefox 69.0 Released
#84For 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...
Even on Android, I was confused by a list of spam "news" on the home page in Firefox 68.0.2. To disable it: Settings, General, Home, Top Sites, disable "Recommended by Pocket".
Re: Firefox 69.0 Released
#85> 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
Re: Firefox 69.0 Released
#86Earlier quoted context omitted.
I'm even OK with this feature, just not with the we're shipping a new “New Tab” page experience that connects you to the best of... drone-speak T_T
Yeah, the best New Tab experience is about:blank.
Re: Firefox 69.0 Released
#87nice
Re: Firefox 69.0 Released
#88> 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…
Re: Firefox 69.0 Released
#89Re: Firefox 69.0 Released
#90> 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?
I use userChrome.css and userContent.css, and I get the nagging feeling that the silent end of that sentence is "...when we eventually replace the code that currently enables user customization with faster, less flexible APIs." (I'm paranoid and FUDing because I care: there's some UX low hanging fruit before they could get rid of userChrome.css. For instance, you need userChrome.css to autohide the toolbar in full sc…