Match Image Encoding capabilities to Android capability
Categories
(Core :: Graphics: ImageLib, enhancement, P3)
Tracking
()
People
(Reporter: colormatch, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 6.2; Win64; x64; rv:71.0) Gecko/20100101 Firefox/71.0
Steps to reproduce:
Currently image encoding capabilities are limited to PNG/JPG/BMP
(as pointed out by Agi )
**Request: **
Match Android's native Image Support capability (minus HEIF, which needs paid license, and maybe minus GIF as I can't think of a reason to be used, unless animated):
https://developer.android.com/guide/topics/media/media-formats#image-formats
Instead of HEIF, add encoding/decoding capabilities for FLIF bug:1240692
(and later maybe push Google to support it as well)
Motivation:
As GV strives not to be a "browser", some capabilities become more significant for applications using GV as engine on which to run on.
The shortcomings of fast decoding of FLIF may not be that important to an app, which works with images and quality and size is much more important than a delay in loading/decoding.
Creating high quality image means the user is paying a steep price in size and resources, and as it may be not important for a browser to be able to encode to WebP or FLIF, image exporting/generating apps, which run on GV will find it crucial.
FLIF also is free software alternative, and may be significant to have it in a long run, considering WebP and HEIF are patented.
PS: Also -Moz's documentation on available image encoders seems to be insufficient/missing at the moment.
Updated•6 years ago
|
Updated•6 years ago
|
Comment 1•6 years ago
|
||
What we are missing from that image encoder table from the ImageLib perspective is WebP. I have no strong opposition. We didn't include it support during the initial implementation as it didn't seem that important. There have been a few related bugs filed about.
Updated•5 years ago
|
Description
•