3 ms·

“Implement WebP image support” – Reported 8 years ago

38 points by xvilka 9y ago

floatboth 9y ago
Holy shit, WebP itself is that old already…
kalleboo 9y ago
JPEG XR always seemed like a better contender to me (I mean WebP launched without alpha channel support. How tone-deaf to developer/designer needs is that?). But it had Microsoft's name on it so it was doomed from the start. At this point it seems like we might as well wait for the eventual "HEIF for AV1" to get the best bang-for-the-buck implementation if we're going to have to support this format in perpetuity.
arusahni 9y ago
Maybe we'll have better luck with the AV1-based alternative [1] that a coalition (i.e., not Google acting unilaterally) is currently designing. [1]: (warning, autoplaying video) https://www.cnet.com/news/google-mozilla-av1-photo-format-could-outdo-aging-jpeg/ https://www.cnet.com/news/google-mozilla-av1-photo-format-co...
- bhouston 9y ago
  Nice. Hopefully the av1 photo format supports transparency.
bhnmmhmd 9y ago
(not directly related to the topic) Firefox (on Mac) lacks three things which I hope they fix them ASAP: 1. Compared to Chrome, FF just makes the Mac insanely hot. Sometimes if a website is stuck at loading, the CPU usage goes seriously high, resulting in temperatures around 80˚ Celsius, and MBP fan rounds at ~5000 rpm. 2. FF doesn't support page scrolling with keyboard shortcuts like Chrome does. On a Mac, you can [big] scroll up/down using alt + arrow keys. "Home" and "End" could also be achieved by Command + arrow keys. On FF however, I haven't found the same shortcuts. Update: It has a weak form of this feature (but still requires your MBP to have "Home" and "End" buttons on it!): https://support.mozilla.org/en-US/kb/keyboard-shortcuts-perform-firefox-tasks-quickly https://support.mozilla.org/en-US/kb/keyboard-shortcuts-perf... 3. FF used to be faster than Chrome at startup, but now on FF 57-58, when you type in the omni-bar, it takes quite a long time for FF to figure out where it has seen this before. In other words, it can't quickly tab-complete what you're typing among bookmarks, history, etc. I switched from Chrome to FF a while ago, mostly because of the Quantum and the new slick modern UI. But due to these annoying problems, I switched back to Chrome.
- romjak 9y ago
  re 2. Have you tried the space bar in FF? I think it does what you want. Can also be reversed with Shift-Space.
- haikuginger 9y ago
  On #2, Fn-up and Fn-down are respectively equivalent to page up and page down on the Mac (at an OS level).
  - bhnmmhmd 9y ago
    Yes, in the "Update" section I addressed that. But still Home and End aren't available. Edit: The comment below mentions another way to achieve Home/End features in FF.
    - Twisol 9y ago
      Are they not? I use Cmd+Up and Cmd+Down to scroll to the top and bottom of a page, respectively, on Firefox.
      - akvadrako 9y ago
        Also fn-Left and fn-Right
      - bhnmmhmd 9y ago
        You're right, I just used them and it works. Weird how Mozilla didn't mention it on the link I provided.
        Twisol 9y ago
        They do, but it might be confusing because they list "Home" and "End" first, before the Cmd+Up/Down alternatives.
- torstenvl 9y ago
  Agreed. Quantum is still very slow on macOS. My least favorite part is the "whoosh to catch up" highlights following the mouse cursor in about:config on my mid-2015 MacBook Pro.
bhouston 9y ago
Also it isn't in Safari and neither is apples new image format.
clouddrover 9y ago
WebP never caught on outside of Google's stack: https://caniuse.com/#search=WebP https://caniuse.com/#search=WebP When Facebook tried to use WebP a while back their users didn't like it: https://www.cnet.com/news/facebook-tries-googles-webp-image-format-users-squawk/ https://www.cnet.com/news/facebook-tries-googles-webp-image-... But these days if you really want to use WebP you can use a WebAssembly build of the library to support it in browsers which don't support it natively: https://webmproject.github.io/libwebp-demo/webp_wasm/index.html https://webmproject.github.io/libwebp-demo/webp_wasm/index.h...
- styfle 9y ago
  Interesting use case for WASM. That really opens the door for more experimental image formats.
- kalleboo 9y ago
  > When Facebook tried to use WebP a while back their users didn't like it That's just a "Google sucks at UX" issue. Apple recently adopted HEIF in iOS wholesale, but nobody is complaining because they made the correct UX call to convert to JPEG as soon as there's the slightest chance the recipient doesn't support the format.
- deleted 9y ago
  [deleted]
jgrahamc 9y ago
WebP does give better image compression in our experience: https://blog.cloudflare.com/a-very-webp-new-year-from-cloudflare/ https://blog.cloudflare.com/a-very-webp-new-year-from-cloudf...
Zekio 9y ago
I would rather they did something about the Scrollbar in firefox, after all that is a thing people have wanted for 17 years
xvilka 9y ago
Opened bug also in Servo, since it is essentially a future of the Firefox https://github.com/servo/servo/issues/20045 https://github.com/servo/servo/issues/20045
ghusbands 9y ago
It happens quite a lot, in general, that some bugs simply don't get the kind of attention they deserve. For example, non-Firefox browsers supported relative positioning of table cells in 2000 or so, which is useful for interactive table rearrangement, and Firefox held fast to not supporting it, citing complications around backgrounds [1], even causing the standard to temporarily change (which they then cite in the bug). List-style-position is still broken [2]. There are plenty more, in all the browsers. [1] https://bugzilla.mozilla.org/show_bug.cgi?id=35168 https://bugzilla.mozilla.org/show_bug.cgi?id=35168 [2] https://bugzilla.mozilla.org/show_bug.cgi?id=36854 https://bugzilla.mozilla.org/show_bug.cgi?id=36854

38 points by xvilka 9y ago

Holy shit, WebP itself is that old already…

JPEG XR always seemed like a better contender to me (I mean WebP launched without alpha channel support. How tone-deaf to developer/designer needs is that?). But it had Microsoft's name on it so it was doomed from the start. At this point it seems like we might as well wait for the eventual "HEIF for AV1" to get the best bang-for-the-buck implementation if we're going to have to support this format in perpetuity.

arusahni 9y ago

Maybe we'll have better luck with the AV1-based alternative [1] that a coalition (i.e., not Google acting unilaterally) is currently designing. [1]: (warning, autoplaying video) https://www.cnet.com/news/google-mozilla-av1-photo-format-could-outdo-aging-jpeg/ https://www.cnet.com/news/google-mozilla-av1-photo-format-co...

bhouston 9y ago
Nice. Hopefully the av1 photo format supports transparency.

bhnmmhmd 9y ago

(not directly related to the topic) Firefox (on Mac) lacks three things which I hope they fix them ASAP: 1. Compared to Chrome, FF just makes the Mac insanely hot. Sometimes if a website is stuck at loading, the CPU usage goes seriously high, resulting in temperatures around 80˚ Celsius, and MBP fan rounds at ~5000 rpm. 2. FF doesn't support page scrolling with keyboard shortcuts like Chrome does. On a Mac, you can [big] scroll up/down using alt + arrow keys. "Home" and "End" could also be achieved by Command + arrow keys. On FF however, I haven't found the same shortcuts. Update: It has a weak form of this feature (but still requires your MBP to have "Home" and "End" buttons on it!): https://support.mozilla.org/en-US/kb/keyboard-shortcuts-perform-firefox-tasks-quickly https://support.mozilla.org/en-US/kb/keyboard-shortcuts-perf... 3. FF used to be faster than Chrome at startup, but now on FF 57-58, when you type in the omni-bar, it takes quite a long time for FF to figure out where it has seen this before. In other words, it can't quickly tab-complete what you're typing among bookmarks, history, etc. I switched from Chrome to FF a while ago, mostly because of the Quantum and the new slick modern UI. But due to these annoying problems, I switched back to Chrome.

romjak 9y ago
re 2. Have you tried the space bar in FF? I think it does what you want. Can also be reversed with Shift-Space.
haikuginger 9y ago
On #2, Fn-up and Fn-down are respectively equivalent to page up and page down on the Mac (at an OS level).
- bhnmmhmd 9y ago
  Yes, in the "Update" section I addressed that. But still Home and End aren't available. Edit: The comment below mentions another way to achieve Home/End features in FF.
  - Twisol 9y ago
    Are they not? I use Cmd+Up and Cmd+Down to scroll to the top and bottom of a page, respectively, on Firefox.
    - akvadrako 9y ago
      Also fn-Left and fn-Right
    - bhnmmhmd 9y ago
      You're right, I just used them and it works. Weird how Mozilla didn't mention it on the link I provided.
      - Twisol 9y ago
        They do, but it might be confusing because they list "Home" and "End" first, before the Cmd+Up/Down alternatives.
torstenvl 9y ago
Agreed. Quantum is still very slow on macOS. My least favorite part is the "whoosh to catch up" highlights following the mouse cursor in about:config on my mid-2015 MacBook Pro.

bhouston 9y ago

Also it isn't in Safari and neither is apples new image format.

clouddrover 9y ago

WebP never caught on outside of Google's stack: https://caniuse.com/#search=WebP https://caniuse.com/#search=WebP When Facebook tried to use WebP a while back their users didn't like it: https://www.cnet.com/news/facebook-tries-googles-webp-image-format-users-squawk/ https://www.cnet.com/news/facebook-tries-googles-webp-image-... But these days if you really want to use WebP you can use a WebAssembly build of the library to support it in browsers which don't support it natively: https://webmproject.github.io/libwebp-demo/webp_wasm/index.html https://webmproject.github.io/libwebp-demo/webp_wasm/index.h...

styfle 9y ago
Interesting use case for WASM. That really opens the door for more experimental image formats.
kalleboo 9y ago
> When Facebook tried to use WebP a while back their users didn't like it That's just a "Google sucks at UX" issue. Apple recently adopted HEIF in iOS wholesale, but nobody is complaining because they made the correct UX call to convert to JPEG as soon as there's the slightest chance the recipient doesn't support the format.
deleted 9y ago
[deleted]

jgrahamc 9y ago

WebP does give better image compression in our experience: https://blog.cloudflare.com/a-very-webp-new-year-from-cloudflare/ https://blog.cloudflare.com/a-very-webp-new-year-from-cloudf...

Zekio 9y ago

I would rather they did something about the Scrollbar in firefox, after all that is a thing people have wanted for 17 years

xvilka 9y ago

Opened bug also in Servo, since it is essentially a future of the Firefox https://github.com/servo/servo/issues/20045 https://github.com/servo/servo/issues/20045

ghusbands 9y ago

It happens quite a lot, in general, that some bugs simply don't get the kind of attention they deserve. For example, non-Firefox browsers supported relative positioning of table cells in 2000 or so, which is useful for interactive table rearrangement, and Firefox held fast to not supporting it, citing complications around backgrounds [1], even causing the standard to temporarily change (which they then cite in the bug). List-style-position is still broken [2]. There are plenty more, in all the browsers. [1] https://bugzilla.mozilla.org/show_bug.cgi?id=35168 https://bugzilla.mozilla.org/show_bug.cgi?id=35168 [2] https://bugzilla.mozilla.org/show_bug.cgi?id=36854 https://bugzilla.mozilla.org/show_bug.cgi?id=36854