5 ms·

AVIF support Firefox issue [1]; Chromium issue [2]. [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1443863 https://bugzilla.mozilla.org/show_bug.cgi?id=14438

• qwerty456127 7y ago
  For some weird reason browser manufacturers strongly oppose adding support for any new media formats. They will only accept a new format once they decide that's a good political move. If I were Google/Mozilla I'd add support for everything ffmpeg and imagemagick support.
  • londons_explore 7y ago
    As soon as they support something, they can never drop support for it because some sites will have started using it, and some sites will never stop using it. Look at how hard it has been to deprecate Flash. By enabling support, they are commiting to maintain same-or-better compatibility pretty much forever. Thats a big commitment if your code is based of someones 'for lolz' patch to ffmpeg...
    • bawolff 7y ago
      Heck, it took until firefox 3.6 to remove xbm support, and that is an utterly terrible image format for a web browser.
      • qwerty456127 7y ago
        > it took until firefox 3.6 to remove xbm support Why would it be a problem to remove if only a small number of little-known sites used it?
        • nitrogen 7y ago
          If memory serves it used to be somewhat common in Unixy land before .png was added to browsers. There may have been long-lived documentation or academic pages with xbm that they were reluctant to break.
          • qwerty456127 7y ago
            Then why remove it anyway? It doesn't seem hard to implement and maintain.