My opinion is that we shouldn't land these patches at this time.

This is essentially for policy reasons:

Running codecs beyond the minimal set we support presents a larger
surface to security review.

Running codecs which other browsers don't support doesn't help web
authors. Our goal is not to inspire web pages 'Best viewed in Firefox'.
Quite the opposite. So adding the wide range of formats gstreamer offers
doesn't advance the web as a platform.

These are the main reasons we haven't added support for codecs like
speex, flac, opus, jpeg2000, jpeg-xr, webp, etc. We have a wav reader in
mozilla-central for debugging, but it's disabled by default.

We have for some years been holding the line against for royalty-free
codecs in HTML against very strong commercial and market pressure,
because the patent terms available for otherwise popular formats like
mp3 and mp4 are incompatible with our principles of user freedom.
Requiring an alternative while flash adoption is falling is an important
check against those commercial interests. Hooking into platform-level
support for those codecs would greatly weaken that stance.

I appreciate the work that's been done on these patches, but unlike
doublec I don't think the code should be in the tree, even disabled by
default. I think the bug should stay open in case we are forced to
reverse our position on mp4, in which case we'll probably want this code
in hurry.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/412647

Title:
  Firefox is not able to play mp4 <video> tags

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/412647/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to