Dear @firefox : Please stop saving images as webp when I drag them out of the browser. Forever stop that. Even if they are webp originally, just give me a setting to auto-convert them to JPEG. When I get a webp file the first thing I have to do is convert it manually if I’m going to do *anything* with it.
I just change the file extension to PNG and call it a day. Somehow it fixes all my compatibility issues.
webp is a great format though…
Exactly, great quality and small file sizes. Perfect to reduce web bloat, or loading times when using things like FoundryVTT
Not really. It is better than shitty JPEG encoders but not really much better than good ones. It’s lossless was fairly good but still barely worth it. Really we should chuck it for JPEG2000 but Google is strong-arming it for unknown reasons.
Google is strong-arming it for unknown reasons.
lol. Yeah it’s a mystery.
jpegxl should be the successor, granted - but that doesn’t make webp any less good
No, but it also doesn’t make it any good to start with.
It’s not really Firefox’s task or problem to convert files from one format to the other, why would it be?
Why is it that the url ends in .JPG but when I right click and save image I can only save it as a .webp?
Because the URL is lying, and the image is not a jpg.
Some CDNs like Akamai and Cloudflare have options to optimize images. We use the Akamai one where I work. It means our creative teams, customers, etc. don’t need to worry too much about whether an image is properly optimized when they upload it. Akamai will, behind the scenes optimize the quality, color palette, and image type (jpg, web, png, etc) and create a number of different versions of the images. Then when a client requests the image Akamai looks at the client device (mobile vs desktop, screen resolution, browser version, etc) and serves the copy of the image that’s best optimized for that device.
So even if the URL ends with .jpg you might be sent a .webp. If you use the browsers developer tool to inspect the response headers you’ll likely see the Content-Type header says it’s .webp as well.
Removed by mod
This post is why we can’t have nice things
Skill issue.
I’m a Linux user and didn’t even notice, let alone care, when I downloaded images as webp because it works just fine with all my other software (Dolphin, Gwenview, GIMP, etc.). There is no problem with webp; who gives a shit?
@grue You don’t need to identify yourself as a Linux user. The insulting remark at the top of your post and the tone of the rest of it makes it clear.
Ever been forced by your workplace to use a piece of software you’d prefer not to? For example, ever tried to share a webp image on MS Teams? You can’t; you have to convert it first. Lots of household-name software rejects the format.
Hopefully the Firefox team needs to care about more than the needs of condescending Linux users.
I also find this insulting even as a linux user myself.
OP you can try GIMP in the meantime as Firefox exports WEBP. There is also a portable version by PortableApps.
Have a nice day, OP.
For example, ever tried to share a webp image on MS Teams? You can’t; you have to convert it first.
That’s funny because the underlying Chromium engine reads WebP files just fine. Write a bug report to Microsoft. The error message is clearly a bug.
It’s not Firefox’s problem that MS Teams (or other “household name” software) sucks.
Edit: ITT: people getting mad at me for pointing out that they’re misattributing the blame.
Agreed. I dislike webp intensely but it’s not firefox’s problem to solve. Be mad at google, not firefox.
@grue Another very productive reply. Great. Enjoy your perfectly cross-compatible software environment that somehow exists despite a lack of compatibility not being a “problem” for any software maker to care about.
You mean I should enjoy my perfectly cross-compatible software environment that exists because the the people making it recognize their responsibility to support the latest standard, rather than acting like proprietary software makers by whining and demanding that everybody else cater to their old, broken shit?
Thanks, I will!
But by all means, continue wallowing in your self-inflicted misery instead if you want. Just don’t get mad at me for not “productively” explaining how to solve your problem, because I have. You just don’t want to hear it.
@grue Stop replying now.
Why are you @ing people? Lemmy uses threaded comment trees, we can see who you are responding to!
Why are you @ing people? Lemmy uses threaded comment trees, we can see who you are responding to!
OP is a Mastodon user who confused an unofficial 3rd party Lemmy community with Mozilla’s bug tracker.
jxl can’t come fast enough.
I prefer PNG because of losless-nes (is that right?). If it’s jpeg, or webp originally, i don’t mind getting the image in that format. But converting/recompression is bad.
It should be spelt “losslessness”. “lossless” is an adjective and when you add “-ness” to an adjective it becomes a noun.
I prefer PNG because it losslessly compresses raster images.
I prefer PNG because it uses a lossless algorithm.
I prefer PNG because I love losslessness.
fortunately, since you use Firefox, there are a handful of extensions available just for this problem already. Maybe not for the drag n drop, though…
@kuneho I love Firefox and dragging images out of the window is a great thing to be able to do, but not when they’re webp.
funny thing is, for some reason, it just… never came to me to just drag images from the browser and save them like that 😅, but surely sounds a logical and convenient thing to do, so I can see your frustration
Report your suggestion on bugzilla.mozilla.org and don’t tag a 3rd party Firefox community.
@woelkchen Thanks for the tip that this is an unofficial community.
WebP images are not bad. Not great, but not bad. The lossless mode is quite good. It is on the software you use to support WebP.
So nothing before 2020, got it. Smh
So nothing before 2020, got it. Smh
Windows supports WebP. Software that uses Windows APIs to read image files has no problem reading those even if it’s from before 2020. I forgot which application it was but in one case changing the file extension was enough for me.
webp is 13 years old. I’ve only heard of Apple not supporting it.
I see others mention some chat apps, weird but ok.
Don’t know where you heard that but it’s wrong.
Which part, I know Safari added support recently but I’m not sure about other components.
Safari, photos’s, finder, preview etc, etc. Across iOS and OS X, since at least last year.
Excellent news :)
If you hate webp because you can’t easily view it, let me recommend ImageGlass as a replacement image viewer for Windows (maybe Linux too, I forget).
