Firefox Notes

First offered to Release channel users on June 10, 2014

View notes for:

Check out "What’s New" and "Known Issues" for this version of Firefox below. As always, you’re encouraged totell us what you think, orfile a bug in Bugzilla. If interested, please see thecomplete list of changes in this release.

We'd also like extend a special thank you to all of thenew Mozillians who contributed to this release of Firefox!

What’s New

  • New

    Sidebars button in browser chrome enables faster access to social, bookmark, & history sidebars

  • New

    Mac OS X command-E sets find term to selected text

  • Changed

    Disallow calling WebIDL constructors as functions on the web

  • Changed

    With the exception of those bundled inside an extension or ones that arewhitelisted, plugins will no longer be activated by default (seeblog post)

  • Developer

    Support for GStreamer 1.0 (see806917 for build configuration)

  • Developer

    Fixes to box-shadow and other visual overflow (seebug 480888)

  • Developer

    Mute and volume available per window when using WebAudio

  • Developer

    background-blend-mode enabled by default

  • Developer

    Use of line-height allowed for <input type="reset|button|submit">

  • Developer

    ES6 array and generator comprehensions implemented (readdocs for more details)

  • Developer

    Error stack now contains column number

  • Developer

    Support for alpha option in canvas context options (featuredescription)

  • Fixed

    Insecure NTLM (pre-NTLMv2) authentication disabled (see828183)

  • Fixed

    Ignore autocomplete="off" when offering to save passwords via the password manager (see956906)

  • Fixed

    TypedArrays don't support new named properties (see695438)

  • Fixed

    Varioussecurity fixes

Known Issues

Try Firefox

  1. Check
  2. Download
  3. Install
  4. Customize

Want to get involved?

Did you know that most of the content in Firefox Support was written by volunteers?
Find out more

Having Problems?

  1. Search for answers on the Firefox Support page
  2. Look at the known issues list and see if we already know about the problem
  3. If you can’t find reference to your issue, please consider filing a technical bug report

Other Resources

Developer Information

Future of Firefox Blog