Firefox 36 Find out what is new

Martin Brinkmann
Feb 24, 2015
Updated • Mar 31, 2015

Firefox 36 will be released to the public on February 24th, 2015 by Mozilla.

All Firefox channels are moved up a version on the release day which means that Firefox Stable installations are moved to version 36, Beta versions to 37, Developer versions to 38 and Nightly installations to 39.

Firefox Extended Support Release builds are also updated to version 31.5 on the day.

The easiest way to find out which version (and channel) of the browser you are running is to type about:support in the browser's address bar.

The page that is loaded displays various information about the browser including the current version and channel under application basics near the top.

Firefox 36 download and update

All Firefox updates are already listed on Mozilla's public FTP server. The updates are made available in two different ways to the general public.

Most Firefox installations will be updated automatically thanks to the browser's built-in update feature.

To check for updates manually tap on the Alt-key on the keyboard and select Help > About Firefox from the menu that opens up.

The second option to obtain the update is to download it from Mozilla once it becomes available on the site.

While it may be tempting to download the release early from the FTP server, last minute changes may invalidate it which can lead to all kinds of issues.

  1. Firefox Beta download
  2. Firefox Developer download
  3. Nightly download

Firefox 36 Changes

Firefox 36 is a minor update in many regards but it includes several important changes under the hood that may impact functionality.

Full HTTP/2 support

This is an important addition to Firefox. HTTP/2 landed recently in its final form which needs to be integrated into web browsers so that users can benefit from it.

HTTP/2 is an update of the original HTTP protocol promising faster browsing, reduced bandwidth usage and secure connection improvements.

While Firefox 36 supports the final h2 protocol for negotiation, not all features of it are implemented in the version as Mozilla engineer Patrick McManus notes on his personal blog.

Partial Media Source Extensions (MSE) support


Partial support for MSE was added to Firefox to support native HTML5 playback on YouTube. A quick check on YouTube revealed that Flash is still used when available in Firefox 36 and that you need to request the HTML5 player if Flash is installed.

If Flash is not installed or if it is disabled, the HTML5 player is automatically used on the site. This implementation is limited to select video resolutions only. You may notice that the highest resolution available is 720p when you use the HTML Flash player on YouTube in Firefox 36.

This changes when you set the parameter media.mediasource.enabled to true.

  1. Type about:config in the address bar and hit enter.
  2. Confirm you will be careful if the prompt appears.
  3. Search for media.mediasource.enabled.
  4. Double-click the entry to set it to true.

Once done, higher resolutions become available on YouTube.

Flash's protected mode sandbox can be disabled on Windows

flash protected mode

Protected Mode runs Flash Player as a low integrity process. While that is useful to most Firefox users, some experienced issues that they linked to protected mode.

You can disable the mode in the Firefox configuration. Mozilla plans to disable the mode completely in Firefox 37.

  1. Type about:config and hit enter.
  2. Find dom.ipc.plugins.flash.disable-protected-mode.
  3. Double-click the preference to set it to true.

The procedure disables protected mode in Firefox. You can verify that this is indeed the case by monitoring Flash process in the Task Manager. If you see plugin-container.exe in the task manager when Flash contents are running it is disabled.

Add-on compatibility changes

Several changes went into Firefox 36 that may affect add-on compatibility. What this means is that some add-ons may stop working completely or partially once you update the browser to version 36 of Firefox.

You find the list of add-on compatibility affecting changes on the official Mozilla blog.

Minor Changes

  • Pinned tiles on the new tab page are included in Firefox Sync.
  • The -remote startup parameter has been removed from Firefox. It was used to execute commands in an already running instance of the browser (e.g. open a new url)
  • Uzbek locale added.
  • Insecure RC4 ciphers are no longer accepted if possible (link)
  • 1024-bit RSA keys are phased out.
  • The Crash Reporter is displayed when the shut down hangs.

Developer Changes

  • Connect Developer Tools and Firefox for Android using WebIDE (link)
  • JavaScript code that is evaluated dynamically can be debugged now (link)
  • Promise rich output in the web console (link)
  • Additional paste options in markup view (link)
  • Support for meta name="referrer" added (link)
  • EMCAScript 6 Symbol data type enabled by default (link)
  • Improved ES6 generators (link)

Firefox for Android

The Firefox 36 for Android update shares the majority of changes with the desktop version of the web browser.

There are only two changes unique to the Android version:

  • Maithili locale added to Android Lollipop devices
  • New Tablet user interface. Additional information about the new tablet UI are available on this website.

Security updates / fixes

Mozilla releases information about security updates and fixes after the final version of Firefox has been available for some time. They are added as soon as they become available.

Additional information / sources

Now Read: Firefox Release Schedule

Firefox 36 Find out what is new
Article Name
Firefox 36 Find out what is new
The article looks at changes and new features of the Internet browser Firefox 36 that was released on Tuesday 25th, 2015.

Tutorials & Tips

Previous Post: «
Next Post: «


  1. chris said on March 4, 2015 at 5:39 pm

    Martin, are you hearing or seeing anything about an issue with Firefox 36? I’m wondering if they stopped pushing it to end users. I saw this:

    1. Martin Brinkmann said on March 5, 2015 at 8:56 pm

      Mozilla just pushed out Firefox 36.0.1

    2. Martin Brinkmann said on March 4, 2015 at 5:56 pm

      It is still offered for all operating systems on the Mozilla website. I cannot say if updates are stopped but I doubt that Mozilla would leave Fx 36 on the site and stop only downloads.

  2. dglp said on March 2, 2015 at 1:17 am

    I’ve just noticed that the search settings drop down format has changed. Is it a v36 change? It’s now difficult or impossible to use.

    1. Where there used to be a single dropdown list of all the search engine addons I’d installed, I now get a grid of about 9. It means I have to go into seach settings and choose the one I want.

    2. For some other reason, the dropdown menu spawns a new page with the search results of the previous engine.

    3. There’s green circle with a white + symbol in it. No idea what this does nor what to do with it.

    Have anyone got a method for reverting these changes?

    1. Martin Brinkmann said on March 2, 2015 at 7:41 am

      The changes were introduced in Firefox 34. You can revert to the old search behavior, more information here:

  3. gb said on February 28, 2015 at 4:58 pm

    Is it possible to disable the “New Tablet user interface” or juste to hide the tab bar an Android ??

  4. Torro said on February 27, 2015 at 7:05 pm

    @Leland – thank you, this worked, fond the adobe plugin and deleted it from a game launcher. FF now shows updated plugin

  5. Rahul Biswal said on February 26, 2015 at 1:13 pm

    Hi Martin,

    Its great to know that Firefox has implemented HTTP/2 support in Firefox 36. I have a question that when will the 64-bit version of Firefox will arrive?

    1. Martin Brinkmann said on February 26, 2015 at 1:31 pm

      No word on that yet as far as I know.

  6. Leland said on February 26, 2015 at 8:42 am

    For those getting false reports of outdated Flash use about:plugins to locate all the plugins it thinks are on your system. You might want to print it for easy reference. Then track each one. Adobe has a bad habit of leaving leftovers behind when updating and I sometimes find a stray .dll plugin that should not be there. Manually delete the file and it should start working like normal. At least it did for me. Good luck.

  7. Daron said on February 26, 2015 at 7:24 am

    I really doesn’t matter any more
    firefox 982 release…please we are tired of that.
    The only update is http/2….period
    all the other updates, is incorporating everything else that
    is available to everyone…in all the other releases….
    please…tell me you have something new to report…

  8. Torro said on February 25, 2015 at 7:37 pm

    For some reason my flash plugin (shockwave flash) keeps saying it is outdated, even after i updated to recent plugin and rebooted.

    Anyone know hoe to fix this?

    1. Torro said on February 26, 2015 at 2:22 am

      @Martin – UNDer Shockwave Flash it says the outdated version, and righ under that is a table that has the following info;

      application/x-shockwave-flash Adobe Flash movie swf
      application/futuresplash FutureSplash movie spl
      application/x-shockwave-flash Adobe Flash movie swf
      application/futuresplash FutureSplash movie spl

      @PJ – ALL websites that use flash says its outdated, and on the Add-Ons manager in the Plugins tab, its also says shockwave is outdated.

      Maybe I didnt update it correctly? Sort of new to Firefox. How does one update shockwave plugin in Firefox properly?

      1. PJ said on February 26, 2015 at 12:07 pm

        @Torro — You can try Adobe’s official Flash Uninstaller. Note that uninstaller version changes with every version of stable Flash release.

        * Flash Uninstaller (v EXE = 938 KB):

        Whichever uninstallation method you use, do check for possible remnants of “Flash” & “Flash Player” folders (see locations mentioned in Seban’s comment). If any found, delete all Flash folders, but take care not to delete the entire Adobe folder & its other contents by mistake.

        Multiple instances of the same/ different versions of the Flash plugin can possibly be caused by your browser being open (or its processes still running) when you install/ update flash.

        How I typically install & perform in-place updates for Adobe Flash:-

        1) Close all browsers. Open Task Manager to make sure that no browser processes are left running in the background.

        2) Download the latest version of the OFFLINE installer. Benefits: No adware/ offers to untick, much faster installation, no internet interruption during installation.

        * Flash Offline Installer for Firefox (v16.0.0.305 EXE = 17.2 MB):

        * For IE, Opera & Chromium browsers, look under the “Still having problems ?” section at the bottom of:

        * For Mac OS X:

        3) Run the offline installer. For version updates in the future, just run the new version of the offline installer for an in-place Flash update (ie. no need to uninstall Flash first if there are no problems).

      2. Martin Brinkmann said on February 26, 2015 at 7:31 am

        I’d start by removing Adobe Flash from the system. Then visit, make sure you uncheck the McAfee offer and click on install now.

      3. Seban said on February 26, 2015 at 6:42 am

        @Torro: I’d try this:
        *Remove Flash via Windows control panel
        *Delete leftovers in
        %appdata%\roaming (look into Macromedia and Adobe folders)
        %appdata%\local (look into Macromedia and Adobe folders)

    2. PJ said on February 25, 2015 at 8:27 pm

      @Torro — Which websites told you that your latest Flash plugin is outdated ? For me, Facebook video will always do that if I disable browser plugin fingerprinting. To avoid getting that “outdated Flash” error, I have to reset the following to the default value (which is an asterisk sign), ie. no choice but to let Facebook snoop on my browser plugins. Perhaps there are other websites that behave in a similar manner.

      about:Config > plugins.enumerable_names = *

    3. Martin Brinkmann said on February 25, 2015 at 7:39 pm

      Have you checked about:plugins to see if more than one is listed by the browser?

  9. Noitidart said on February 25, 2015 at 11:19 am

    Do you know where the bugzilla topic is for removing the “-remote” I relied on that for my next release of Profilist

    1. Martin Brinkmann said on February 25, 2015 at 11:36 am
  10. Jonny said on February 25, 2015 at 8:07 am

    I just updated to 36 and FF kept freezing for 10-20 seconds at random and when any link is opened in a new tab. Went back to 35.0.1.

  11. Chains The Bounty Hunter said on February 25, 2015 at 5:35 am

    Still no full MSE support. I’m fine with limited resolutions on HTML5 until they get that stuff stable/fully implemented. It’s Chrome catch-up time where it counts vs. cosmetic bologna.

  12. Ustavio said on February 24, 2015 at 10:26 pm

    The Flash plug in disappeared completely on this update. It’s odd though, out of five different systems, the plug in vanished from just one and only from Firefox. The three user accounts (admin and standard) no longer have flash at all. It was the most current version and there was no indication that it was blocked. Just plain odd.

    1. Boris said on February 24, 2015 at 11:12 pm

      Flash pretty much stayed on On my System Windows 8.1 64bit.

      But suddenly I had problem saving files. It got fixed after another restart, but still pretty weird. Never had this problem before on Firefox.

  13. anonymous said on February 24, 2015 at 7:59 pm

    Has Firefox Hello been improved upon in this release?

    1. Martin Brinkmann said on February 24, 2015 at 8:48 pm

      Since it is not listed in the release notes, I doubt it.

  14. wz said on February 24, 2015 at 6:10 pm

    Why does the 36.0 source size(382M)more than double compared to 35.0(168M)

  15. Niks said on February 24, 2015 at 2:53 pm

    What about electrolysis ? It was supposed to land in v36.

    1. Nickname said on February 24, 2015 at 4:16 pm

      It was never supposed to land in 36

      1. Haider said on February 25, 2015 at 10:17 am

        On which release should we expect the electrolysis?

        I thought should be here because it is by default enabled in nightly v. 36.

    2. Martin Brinkmann said on February 24, 2015 at 3:00 pm

      No not there yet. Will take some time before it lands.

  16. rsn said on February 24, 2015 at 12:36 pm

    Is about:preferences enabled by default or just like 35 only manually?

    1. Martin Brinkmann said on February 24, 2015 at 12:46 pm

      It is not enabled by default, you still need to load it manually.

      1. PJ said on February 25, 2015 at 8:12 pm

        Hmm, about:Preferences does not seem to be fully functional, at least in my case.

        For instance, the proxy setting configured via about:Preferences#Advanced will not stick, regardless of whether Firefox is used in normal or safe mode. I also tried doing that using different good backup copies of pref.js, but to no avail.

        If the Tools > Options modular menu is disabled, below is only way to change the proxy option:-
        About:Config > network.proxy.type = 5 [default: System proxy] or 1 [Manual proxy]

        Although I prefer using about:Preferences tab over the modular menu, I found the above issue such a logistical & human-memory hassle that I reverted about:Config > browser.preferences.inContent to false [default].

      2. rsn said on February 24, 2015 at 1:23 pm

        Thanks ;) Idk what are they waiting for, seems fully functional for me :S

Leave a Reply

Check the box to consent to your data being stored in line with the guidelines set out in our privacy policy

We love comments and welcome thoughtful and civilized discussion. Rudeness and personal attacks will not be tolerated. Please stay on-topic.
Please note that your comment may not appear immediately after you post it.