You Got A Question? Ask    GNOME Community!

Firefox 24 released with extended support

This post was made with an older stylesheet

It’s been a long time since Firefox developers decided that it would be better to release more often taking care of various security holes, implementing new features and fixing any bugs along the way. This though couldn’t come without an extended support version that organizations, schools and other adopters who need extended support for mass deployments would choose to use.

The first ESR was Firefox 10, then 17, and now we come to Firefox 24 ESR. This version gets all the new features and performance enhancements that happened from version 17 till now, and will be supported with point releases that contain only security updates. This support will continue until Firefox 31 will be released with two cycle (12 week) overlap between the time of a new release and the end-of-life of the previous release to permit testing and certification prior to deploying a new version.


Firefox 24

The new version of Firefox brings a new useful option called “close tabs to the right” that allows users to massively close all tabs positioned to the right of their cursor (or the tab that the command is given).


As developers explain:

Why “close tabs to the right” and not “close tabs to the left”? When we open new tabs they appear on the end, and so naturally tabs that have a longer lifetime end up being promoted to the start-side of the bar. This leads us towards the situation where closing tabs “to the right” is a simple way of closing the ephemeral tabs.

On the accessibility news, the corresponding API was enriched with a way to distinguish a pinned tab from a non-pinned one. Also, major SVG rendering improvements around image tiling and scaling were completed. What matters most on an extended release are the security fixes though, so here is a list with security issues that no longer concern Firefox:

Critical importance:

  • (MFSA 2013-92) – GC hazard with default compartments and frame chain restoration
  • (MFSA 2013-90) – Memory corruption involving scrolling
  • (MFSA 2013-89) – Buffer overflow with multi-column, lists, and floats
  • (MFSA 2013-81) – Use-after-free with select element
  • (MFSA 2013-79) – Use-after-free in Animation Manager during stylesheet cloning
  • (MFSA 2013-78) – Integer overflow in ANGLE library
  • (MFSA 2013-76) – Miscellaneous memory safety hazards (rv:24.0 / rv:17.0.9)

High importance:

  • (MFSA 2013-88) – compartment mismatch re-attaching XBL-backed nodes
  • (MFSA 2013-87) – Shared object library loading from writable location
  • (MFSA 2013-83) – Mozilla Updater does not lock MAR file after signature verification
  • (MFSA 2013-82) – Calling scope for new Javascript objects can lead to memory corruption

Moderate importance:

  • (MFSA 2013-91) – User-defined properties on DOM proxies get the wrong “this” object
  • (MFSA 2013-86) – WebGL Information disclosure through OS X NVIDIA graphic drivers
  • (MFSA 2013-85) – Uninitialized data in IonMonkey
  • (MFSA 2013-84) – Same-origin bypass through symbolic links
  • (MFSA 2013-80) – NativeKey continues handling key messages after widget is destroyed
  • (MFSA 2013-77) – Improper state in HTML5 Tree Builder with templates

  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