You Got A Question? Ask    GNOME Community!


Firefox 28 Advancing Video Technologies

Another short-term support version of Firefox is out and if you’re not using version 24 it is recomended that you upgrade to get the latest security and bug fixes, along with exciting new implementations introduced in 28.

Among the highlights is the implementation of VP9 video decoding, the new HTML5 horizontal audio and video control and the support for Opus format in WebM.

opusvp9webm-19 15:54:09

It’s only 240p and it looks way better than expected!


So, let me just say a few words about those new (for Firefox) web content formats. VP9 is a royalty-free work of Google, and is basically a video compression format. What is hoped is that VP9 will help in the higher resolution videos category while remaining relatively light for bandwidth. Specifically, Google aims for 50% bitrate reduce at the same quality.

Higher resolution video means something around 4k which is coming soon on selective YouTube content and is already a reality for some TVs called Ultra High Definition.If you are using Chrome, you had the ability to decode VP9 since December 2012, but now Firefox finally synchronized with the technology.

Opus on the other hand is a lossy audio compression format that is also open source. Opus can handle a wide range of audio applications, including Voice over IP, video-conferencing, in-game chat, and even remote live music performances. It can scale from low bit-rate narrowband speech to very high quality stereo music.

800px-Opus_quality_comparison_colorblind_compatible.svg


A new web browser version release can never come without the security related fixes, so here is a list with security issues that no longer concern Firefox:

Critical importance:

  • (MFSA 2014-32) – Out-of-bounds write through TypedArrayObject after neutering
  • (MFSA 2014-31) – Out-of-bounds read/write through neutering ArrayBuffer objects
  • (MFSA 2014-30) –  Use-after-free in TypeObject
  • (MFSA 2014-29) –  Privilege escalation using WebIDL-implemented APIs
  • (MFSA 2014-15) – Miscellaneous memory safety hazards (rv:28.0 / rv:24.4)

High importance:

  • (MFSA 2014-28) – SVG filters information disclosure through feDisplacementMap
  • (MFSA 2014-26) – Information disclosure through polygon rendering in MathML
  • (MFSA 2014-17) – Out of bounds read during WAV file decoding

Moderate importance:

  • (MFSA 2014-27) – Memory corruption in Cairo during PDF font rendering
  • (MFSA 2014-25) – Firefox OS DeviceStorageFile object vulnerable to relative path escape
  • (MFSA 2014-24) – Android Crash Reporter open to manipulation
  • (MFSA 2014-22) – WebGL content injection from one domain to rendering in another
  • (MFSA 2014-21) – Local file access via Open Link in new tab
  • (MFSA 2014-19) –  Spoofing attack on WebRTC permission prompt
  • (MFSA 2014-16) – Files extracted during updates are not always read only

Firefox Homepage


 
  We can't watch comments unless G+ provides an API or if you send a notification, e.g +World Of Gnome
     Sometimes is better to place your questions on GNOME Community