Firefox 62.0 Beta Brings CSS Variable Fonts, "Clear Site Data & Cookies" Option

[phoronix]

Phoronix: Firefox 62.0 Beta Brings CSS Variable Fonts, "Clear Site Data & Cookies" Option

Following yesterday's release of Firefox 61, Mozilla pumped Firefox 62 into the beta channel...

http://www.phoronix.com/scan.php?page=news_item&px=Firefox-62-Beta

[schmidtbag]

I'm surprised the "Clear Site Data & Cookies" feature wasn't implemented like... 10 years ago. Seems kinda obvious to me.
Also, I don't understand the point of implementing their own TTS. Every modern OS has TTS options - why can't they just reference those externally? Just seems like unnecessary bloat.

[haplo602]

I just hope they will make the button ask you if you want one or the other or both ...

[uid313]

Also, I don't understand the point of implementing their own TTS. Every modern OS has TTS options - why can't they just reference those externally? Just seems like unnecessary bloat.

The article said they are enabling their TTS API, not about implementing any custom engine of their own.
Their TTS API might just be a wrapper that uses the underlying TTS engine on the platform it runs on.

[shmerl]

It also enables WebRender, which is hard to notice: https://bugzilla.mozilla.org/show_bug.cgi?id=1432515

Switching it on is a bit convoluted though. I had to use env variable for that:

MOZ_WEBRENDER=1

Setting these in about:config alone didn't work:

gfx.webrender.all.qualified = false
gfx.webrender.enabled = true

[andyprough]

I just hope they will make the button ask you if you want one or the other or both ...

I just want a hamburger button that brings me an actual cheeseburger to my desk for me.

[johnp117]

It also enables WebRender, which is hard to notice: https://bugzilla.mozilla.org/show_bug.cgi?id=1432515

It doesn't enable WebRender, it just includes it and it is disabled by default. They will start experimentally enabling it on Nightly for the first target group (Win10+Nvidia) next month. `gfx.webrender.all.qualified;true` only enables WebRender if on such qualified hardware, `gfx.webrender.{all,enabled}` only work on Nightly and as you found out, flipping the env variable allows circumventing the qualified hardware check and is only meant for the continuous integration tests. Details

[shmerl]

It doesn't enable WebRender, it just includes it and it is disabled by default.

Enables in the build. I said above, that you need to turn it on at runtime.

`gfx.webrender.all.qualified;true` only enables WebRender if on such qualified hardware, `gfx.webrender.{all,enabled}` only work on Nightly and as you found out, flipping the env variable allows circumventing the qualified hardware check and is only meant for the continuous integration tests. Details

Is there any way to enable it in beta without using the environment variable?

[oibaf]

It will also enable the TLS API, useful for re-enabling extension like CipherFox and SSLeuth:

https://bugzilla.mozilla.org/show_bug.cgi?id=1322748

[Mike Frett]

I'm surprised the "Clear Site Data & Cookies" feature wasn't implemented like... 10 years ago. Seems kinda obvious to me.
Also, I don't understand the point of implementing their own TTS. Every modern OS has TTS options - why can't they just reference those externally? Just seems like unnecessary bloat.

It's always been under the "Clear Recent History" option.