Firefox 65.0 Released With WebP Support, Better Security

[Vistaus]

`browser.tabs.drawInTitlebar` or `MOZ_GTK_TITLEBAR_DECORATION` environment variable

The env var I understand, but browser.tabs.drawInTitlebar... I thought that setting only worked on Windows?

[johnp117]

That sucks, I hope CSD can be disabled in about:config, [...]

`browser.tabs.drawInTitlebar` or `MOZ_GTK_TITLEBAR_DECORATION` environment variable

[skeevy420]

Headerbar will be default from 66 on: https://www.omgubuntu.co.uk/2019/01/...csd-by-default

That sucks, I hope CSD can be disabled in about:config, CSS, or that the Menu>Customize>Title Bar option is still present. I really don't want to drop Firefox over something as silly as forced CSD...but I just do not like the CSD style or look nor do I like the extra steps of the hamburger over a File Edit Options Help header. I feel about CSD the way a lot of people feel about systemd.

IMHO, CSD can be fine for simple stuff and programs that are very well laid out, probably by a dedicated design team; but programs with lots of advanced settings can become jumbled messes and compacting everything into the hamburger is damn annoying...might as well just hide the hamburger in a right click menu or a long press hidden menu if we're that worried about screen space.

CSD reminds me of using a car with a crappy menu system on the radio -- it adds extra steps and layers to make stuff seem more organized when all it really does is slows down one's workflow by adding all those extra clicks and steps to find stuff. At least that's my impression of CSD from a mouse user's perspective. It's also damn annoying when you go to drag a window around and you click the wrong part of the CSD header because an extra tab ate up grab space.

Personally, on displays over 13" with at least a 768 verticle resolution, CSD makes no sense whatsoever. Most of my QT programs can be configured to use less space with a minimal sized titlebar and the default File Edit header than GTK CSD programs use with everything combined. It's amazing how much space can be saved by tweaking KDE's default font sizes and KWin's title bar size.

I guess it's time to dance on the grave of JPEG and PNG, and I'm glad the time has finally come, as I've been waiting for years for this to happen.

[andreano]

> AV1 decoder is now enabled by default…

For Windows users only!

About that: At time of writing, Mozilla still haven't enabled dav1d's assembly optimizations on Windows: https://bugzilla.mozilla.org/show_bug.cgi?id=1521062

I hope someone just forgot to update the issue tracker, instead of breaking YouTube for Windows users…

[Grinch]

Why did they even waste time with WebP? The endgame (for this decade) is AVIF.

WebP is great for lossless image compression (much better than the current 'de facto' lossless standard which is PNG), AVIF is likely going to be great for lossy image compression.

[Vistaus]

I’m most excited about further wayland and headerbar integration.

Headerbar will be default from 66 on: https://www.omgubuntu.co.uk/2019/01/...csd-by-default

[wswartzendruber]

Why did they even waste time with WebP? The endgame (for this decade) is AVIF.

[Grinch]

I think flif is much better. http://flif.info/
And bpg is better when lossy.

FLIF offers slightly better compression, but it is much slower in both compressing and decompressing. BGP, being based upon HEVC, requires patent royalties, so it is dead. Apple supports HEVC through HEIF on their platforms, but again it's not gaining any traction outside of the Apple ecosystem due to patents/royalties.

For a lossy replacement for JPEG, I can think of two possible candidates:

First off we have AVIF which is based upon AV1, and thus royalty free. The second one is PIK which is a image codec from the same people who made WebP, but with better results for lossy, also it is able to losslessly recompress JPEG files with the resulting PIK file becoming ~22% smaller, royalty free as well.

[ipsirc]

Furthermore it's the best lossless image format in terms of compression ratio/decompression speed (blows PNG out of the water on both metrics) so there are serious savings here to be had.

I think flif is much better. http://flif.info/
And bpg is better when lossy. http://xooyoozoo.github.io/yolo-octo...3&webp=t&bpg=t