Firefox 46

< Releases
  • 1Summary
    • 1.6QA Activities
  • 2Milestones
    • 2.2Betas
      • 2.2.1Beta 1
      • 2.2.2Beta 2
      • 2.2.4Beta 4
      • 2.2.5Beta 5
      • 2.2.6Beta 6
      • 2.2.7Beta 7
      • 2.2.8Beta 8
      • 2.2.9Beta 9
      • 2.2.10Beta 10
      • 2.2.11Beta 11
    • 2.3Release Candidates
      • 2.3.146.0 RC1 (build 3)
      • 2.3.246.0 RC2 (build 4)
      • 2.3.346.0 RC3 (build 5)
      • 2.3.4Release 46.0
      • 2.3.546.0.1 Build 1

Firefox 46.0.1; More system details Additional System Details Installed Plug-ins. Coupons, Inc. Coupon Printer 5.0.2.5 Foxit Reader Plug-In For Firefox and Netscape Google Update Intel web components updater - Installs and updates the Intel web components Intel web components for Intel® Identity Protection Technology.

This page is to track testing of Firefox 46 from mozilla-central (Nightly) through to mozilla-release. This is intended to be a minimal set of information to help Firefox QA understand and communicate the quality of upcoming releases. Our current walkthrough of the release and QA process might be changing due to recent reorgs.

Schedule

May 04, 2016. Security vulnerabilities of Mozilla Firefox version 46.0.1 List of cve security vulnerabilities related to this exact version. You can filter results by cvss scores, years and months. This page provides a sortable list of security vulnerabilities. Read about new Firefox features, and get tips for staying safer online. Firefox Release. April 26, 2016. Version 46.0, first offered to Release.

Please consult the Rapid Release Calendar for more information.

Milestone Date Checks
Nightly 2015-12-14 Conduct daily stability and bug triage, ensure features are owned
Aurora Migration 2016-01-25 Conduct testing to ensure Firefox 46 Aurora builds are okay, sign off for updates on Friday
Aurora Updates enabled 2016-01-29 Continue daily stability and bug triage, ensure features are tested
Beta Uplift 2016-03-07 Review testing and sign off every beta release
Release 2016-04-19 Review tests and sign off release

Meetings

Meeting Purpose When Vidyo Room IRC Backchannel
Channel Status Raise quality concerns with the Release Management team 10:00 Pacific on Tuesday & ThursdayReleaseCoordination#planning
Firefox QA Meet the Desktop QA team and hear what they're working on8:30am Pacific on WednesdaysDesktopQA#qa
QA Team Meet the entire QA team and hear what they're working on!1:30am Pacific on WednesdaysQA#qa

Nightly

During the 6 weeks that Firefox 46 is on the Nightly channel, QA will focus on helping with the Firefox iteration planning, as well as with crash reporting and triaging newly reported bugs. The earlier we can get these bug reports into shape for developers to prioritize them and work on them, the more likely they'll be fixed by release in April.

Reference: https://wiki.mozilla.org/QA/Desktop_Firefox/Walkthroughs/Release_Coordination#Nightly

Questions for workweek
  • Each topcrash should have a developer assigned, a QA contact, and tracking + or -.
  • We should decide on a threshold for 'crisis' level crash spikes/crash rates. (Different for startup, plugin, crashes or specific platforms)
  • What do we want to do with the iteration process. Continue assigning QA contact, verification + or -?
  • We should encourage the use of 'feature' or verification needed keywords/flags.
  • What, if any, conditions would actually block or delay the move to aurora?
End of cycle status
  • Total bugs filed affecting 46:
  • Bugs fixed / verified on 46:
  • Conditional signoff for merge: (date, who signed off)
  • QE signoff:

Developer Edition (Aurora)

Continue triaging incoming bugs with community help. Test e10s issues.

During the 46 Developer Edition cycle we will be working to help determine the state of the Electrolysis (e10s) project. e10s will be ready to move to Beta if stability and fixes are up to an acceptable quality level.

  • File crashes, escalate bad crashes.
  • Track feature milestones (for example the e10s tracking flags.)
  • Should have testing plans for features that we know may be turned off /on conditionally.
  • link to release notes. review & update.

Reference (and migration / signoff plan: https://wiki.mozilla.org/QA/Desktop_Firefox/Walkthroughs/Release_Coordination#Aurora)

Beta

During the Beta cycle, there are at least 9 beta releases. Communication with the release coordination, release engineering, and automation teams is key.

QA analyzes the results of functional, remote, and update tests running on jenkins. We create config files for the update tests, check their validity on mciconf and run them on at least two channels for each beta release cycle. A big part of this work currently is going through the test results to figure out why test failures occurred (infrastructure, tests themselves, actual Firefox bug).

Pivotal bugs may need verification during each beta cycle.

  • link to release notes. review & update.
  • crash evaluation/escalation.
  • feature evaluation.

QA Activities

QA wanted

The following tracks bugs which have requests for urgent QA assistance.

  • Choose a bug to test from the list below
  • Read it and make sure you understand what information is needed (this may be steps or URLs to reproduce, a regression range, or something else altogether)
  • Use the latest build of this Firefox version and test until you've discovered the information necessary. Ask for help if you need it.
  • Report this information to the bug and remove the qawanted keyword

Firefox 46.0 Download Filehippo

No results.

0 Total;0 Open (0%);0 Resolved (0%);0 Verified (0%);


Stability

This section tracks bugs representing the most urgent stability issues. Consult this wiki for more information.

  • Ensure new and explosive crashes have actionable bug reports which are in progress
  • Top Crashes - ensure the highest ranked crashes have actionable bug reports which are in progress
  • Untriaged Bugs - ensure bugs are actionable and in the correct component

Unconfirmed Bug Triage

The following tracks triage and testing of incoming, unconfirmed bug reports.

  • Choose a bug to test from the list below
  • Use the latest Nightly build to confirm the bug reproduces
  • Flag with reporter with needinfo if you cannot reproduce and need more information
  • Set the status to NEW and ensure the bug is in the appropriate component if you can reproduce the bug (provide as much detail about your testing as possible)
  • If it's a Firefox bug you may want to add the firefox-backlog=? flag to it.

Queries:

  • All Unconfirmed Bugs
  • Unchanged Since One Week
    • These bugs may need extra attention.
  • Unchanged Since One Month
    • These are likely to be confusing or non-reproducible issues. We should make decisions to either close these or tag these unactionable, and filter them out

Verification Needed Bugs

  • Review the bugs below in the Pending Triage section and select a bug you want to test
  • Make sure you understand the bug before you begin testing it
  • Test on a previously known broken build to make sure you can reproduce the bug
  • Test on the latest build from the branches which are fixed to confirm the bug no longer reproduces
  • Mark the bug VERIFIED FIXED if the bug appears to be fixed and set the appropriate status-firefox flag to verified
  • Reopen the bug if it still reproduces

Iteration Development

Firefox development during Nightly works on two-week iterations as of 2014. This section tracks the bugs selected for development in these iterations.Please consult the Iteration Dev Walkthrough and the Firefox/IterativeDevelopment page for more information on this process.

  • Ensure all bugs are marked qe-verify:+ or -
  • Ensure all qe-verify:+ bugs have a QA Contact (The Feature Owner page may help here)
  • Ensure all selected bugs are VERIFIED before the end of the iteration
  • Anything incomplete at the end of the iteration will be automatically carried over to the next iteration

Queries:

  • Dashboard showing current active iteration: https://crash-analysis.mozilla.com/rkaiser/crash-report-tools/qa/
  • Iteration 46.1, all bugs: https://bugzilla.mozilla.org/buglist.cgi?f1=OP&j1=OR&f2=cf_fx_iteration&o2=substring&v2=46.1&f3=status_whiteboard&o3=substring&v3=s%3D46.1&f4=CP
  • Iteration 46.2, all bugs: https://bugzilla.mozilla.org/buglist.cgi?f1=OP&j1=OR&f2=cf_fx_iteration&o2=substring&v2=46.2&f3=status_whiteboard&o3=substring&v3=s%3D46.2&f4=CP
  • Iteration 46.3, all bugs: https://bugzilla.mozilla.org/buglist.cgi?f1=OP&j1=OR&f2=cf_fx_iteration&o2=substring&v2=46.3&f3=status_whiteboard&o3=substring&v3=s%3D46.3&f4=CP

Aurora Migration

Post-merge Work (as soon as updates are disabled):

  • [DONE] MM-CI - configure the mozilla-aurora_update testrun on MM-CI to use the auroratest channel (before first Aurora builds are generated, to make sure we don't get any red on aurora update tests)

Pre-sign-off Checks:

  • [DONE] Features - all scoped features are signed off as ready for Aurora by owners. (If you haven't heard anything to the contrary, that is probably true, but make sure we don't know of blocking issues.)
  • [DONE] Bugs - document and review any reported bugs and issues, nominate them for tracking if serious (i.e. make sure all bugs needed to be tracked have at least a request for that up).
  • [DONE] Stability - review crash stats before sign-off to raise any red flags.
  • [DONE] L10n - contact L10n drivers (usually :Pike) to see if there are any known localization issues.

Post-sign-off Checks (as soon as updates are enabled again):

  • [DONE] MM-CI - configure the mozilla-aurora_update testrun on MM-CI to use the aurora channel
  • [NOT STARTED] Updates - previous versions of Aurora update to the new version (check a few old builds manually once next round of new builds is available)

Betas

Beta 1

Build Information

  • Build 4: 46.0b1-build4 fb3494d06dfb (ID: 20160307215824)
  • Build 8: 46.0b1-build8 fb3494d06dfb (ID: 20160307215824)

Testing

  • Manual - Firefox 46 Beta 1
    • [DONE]46.0b1-build4 Smoke Testing with focus on APZ.
    • [DONE]46.0b1-build8 Smoke Testing with focus on Web Compatibility.
    • [DONE]Bug verification with focus on the latest fixes to land in this build.
  • Automated (configs for ondemand, build8)
    • [DONE] Updates on beta-cdntest channel (report) - PARTIAL: en-US is fine, localized builds for some locales broken due to bug 1255811
    • [DONE] Updates on beta channel (report) - en-US is fine, other locales still seem to get 45 RC as expected

Beta 2

Build Information

  • Build 2: 46.0b2-build2 2a62a6f3237e (ID: 20160314144540)
  • Build 3: 46.0b2-build3 5904e3eb711d (ID: 20160316065941)

Testing

  • Manual - Firefox 46 Beta 2
    • [DONE]46.0b2-build3 Regression Testing with focus on Search, Search suggestions and the Awesomebar.
    • [DONE]Bug verification with focus on the latest fixes to land in this build.
  • Automated (configs for ondemand)
    • [NOT STARTED] Updates on beta-cdntest channel (report)
    • [NOT STARTED] Updates on beta channel (report)

Beta 3

Beta 4

Build Information

  • Build 1: 46.0b4-build1 ccd48b57944a (ID: 20160321115535)
  • Build 2: 46.0b4-build2 2f6f69a19150 (ID: 20160322075646)

Testing

  • Manual - Firefox 46 Beta 4
    • [DONE]46.0b4-build1 Regression Testing targeting audio/video compatibility and the crash reporter.
    • [DONE]Bug verification with focus on the latest fixes landed in beta.
  • Automated (configs for ondemand)
    • [DONE] Updates on beta-cdntest channel (report)
    • [DONE] Updates on beta channel (report)

Beta 5

Firefox 46 download

Build Information

  • Build 2: 46.0b5-build2 53d6e6648f97 (ID: 20160324011246)

Testing

  • Manual - Firefox 46 Beta 5
    • [DONE]46.0b5-build2 Regression Testing targeting Printing, Themes, Toolbar Customization and WebGL.
      • The build has been CONDITIONALLY SIGNED OFF because of 1259729.
    • [DONE]Bug verification with focus on the latest fixes landed in beta.
  • Automated (configs for ondemand)
    • [DONE] Updates on beta-cdntest channel (report)
    • [DONE] Updates on beta channel (report)

Beta 6

Build Information

  • Build 1: 46.0b6-build1 97b81104ac03 (ID: 20160328182534)

Testing

  • Manual - Firefox 46 Beta 6
    • [DONE]46.0b6-build1 Regression Testing targeting audio compatibility and migration.
      • The build has been CONDITIONALLY SIGNED OFF because of 1260701.
    • [DONE]Bug verification with focus on the latest fixes landed in beta.
  • Automated (configs for ondemand)
    • [NOT STARTED] Updates on beta-cdntest channel (report)
    • [NOT STARTED] Updates on beta channel (report)

Beta 7

Build Information

  • Build 2: 46.0b7-build2 191f5eb4cbd7 (ID: 20160401021843)

Testing

  • Manual - Firefox 46 Beta 7
    • [DONE]46.0b7-build1 Regression Testing targeting Places, PDF compatibility, Image support.
    • [DONE]46.0b7-build2 Smoke Testing targeting Hello add-on v1.2.2.
      • The build has been CONDITIONALLY SIGNED OFF because of the following bugs: http://mzl.la/1q0aQqI.
    • [DONE]Bug verification with focus on the latest fixes landed in beta.
  • Automated (configs for ondemand)
    • [DONE] Updates on beta-cdntest channel (report)
    • [DONE] Updates on beta channel (report)

Beta 8

Build Information

  • Build 1: 46.0b8-build1 0334bcac4033 (ID: 20160404120533)

Testing

  • Manual - Firefox 46 Beta 8
    • [DONE]46.0b8-build1 Regression Testing targeting Plug-in Compatibility, Downloads, Safe Browsing and Session Restore.
      • The build has been CONDITIONALLY SIGNED OFF because Bug 1259482 still reproduces intermittently, and 3 new issues were found for Hello (not blockers).
    • [DONE]Bug verification with focus on the latest fixes landed in beta.
  • Automated (configs for ondemand)
    • [DONE] Updates on beta-cdntest channel (report)
    • [DONE] Updates on beta channel (report)

Beta 9

Build Information

  • Build 1: 46.0b9-build1 b007110e9005 (ID: 20160407053945)

Testing

  • Manual - Firefox 46 Beta 9
    • [ON TRACK]46.0b9-build1 Regression Testing targeting OS X Signing, OS X 32-bit mode, Hello add-on (v1.2.4).
    • [ON TRACK]Bug verification with focus on the latest fixes landed in beta.
  • Automated (configs for ondemand)
    • [DONE] Updates on beta-cdntest channel (report)
    • [DONE] Updates on beta channel (report)

Beta 10

Build Information

  • Build 1: 46.0b10-build1 9ea83990839b (ID: 20160411042519)

Testing

  • Manual - Firefox 46 Beta 10
    • [DONE]46.0b10-build1 Regression Testing targeting Sync, Default browser settings and Hello (Loop).
    • [DONE]Bug verification with focus on the latest fixes landed in beta.
  • Automated (configs for ondemand)
    • [DONE] Updates on beta-cdntest channel (report)
    • [DONE] Updates on beta channel (report)

Beta 11

Build Information

  • Build 1: 46.0b11-build1 076bf6a0ac85 (ID: 20160414152344)

Testing

  • Manual - Firefox 46 Beta 11
    • [DONE]46.0b11-build1 Regression Testing targeting Video Playback.
    • [DONE]Bug verification with focus on the latest fixes landed in beta.
  • Automated (configs for ondemand)
    • [DONE] Updates on beta-cdntest channel (report)
    • [DONE] Updates on beta channel (report)

Release Candidates

46.0 RC1 (build 3)

Build Information

  • Build 3: 46.0RC-build3 521d7102e93d (ID: 20160418114253)

Testing

  • Manual - Firefox 46.0 RC1
    • [DONE]Smoke Testing with focus on Web Compatibility.
    • [DONE]Bug verification with focus on the latest fixes to land in this build.
  • Automated (configs for ondemand)
    • This is a condidate for the 46.0 release build. We should test updates on beta-cdntest for a preliminary sign-off (Release Management must give the 'go' for pushing to beta), then on beta after the push to beta, and then on the day before release (Monday), after a full sign-off and push to that channel, run tests on release-cdntest.
    • [DONE] Updates on beta-cdntest channel (report)
    • [DONE] Updates on beta channel (report)

46.0 RC2 (build 4)

Build Information

  • Build 4: 46.0RC-build4 53f1fadd9d33 (ID: 20160420024437)

Testing

  • Manual - Firefox 46.0 RC2
    • [DONE]Smoke Testing with focus on Web Compatibility and the Password Manager.
    • [DONE]Bug verification with focus on the latest fixes to land in this build.
  • Automated (configs for ondemand)
    • This is a condidate for the 46.0 release build. We should test updates on beta-cdntest for a preliminary sign-off (Release Management must give the 'go' for pushing to beta), then on beta after the push to beta, and then on the day before release (Monday), after a full sign-off and push to that channel, run tests on release-cdntest.
    • [DONE] Updates on beta-cdntest channel (report)
    • [DONE] Updates on beta channel (report)

46.0 RC3 (build 5)

Build Information

  • Build 5: 46.0RC-build5 078baf501b55 (ID: 20160421124000)

Testing

  • Manual - Firefox 46.0 RC3
    • [DONE]Smoke Testing with focus on Search.
    • [DONE]Bug verification with focus on the latest fixes to land in this build.
  • Automated (configs for ondemand)
    • This is a condidate for the 46.0 release build. We should test updates on beta-cdntest for a preliminary sign-off (Release Management must give the 'go' for pushing to beta), then on beta after the push to beta, and then on the day before release (Monday), after a full sign-off and push to that channel, run tests on release-cdntest.
    • [DONE] Updates on beta-cdntest channel (report)
    • [DONE] Updates on beta channel (report)
    • [DONE] Updates on release-cdntest channel (report)
    • [DONE] Updates on release channel (report)

Release 46.0

Build Information

  • See Release Candidate Build 5

Testing

  • Update Testing - see Release Candidate Build 5
  • Throttle Testing (see Walkthrough for details)
    • Used commands:
    • Results
      • After release push (expected to be @ 25%), 2016-04-26: Win32: 23% - Win64: 24% - Mac: 29% - Linux32: 21% - Linux64: 30%
      • After disabling updates (expected to be @ 0%), 2016-04-27: Win32: 0% - Win64: 0% - Mac: 0% - Linux32: 0% - Linux64: 0%
      • After fully enabling updates (expected to be @ 100%): N/A - updates not re-enabled (dot release planned)

46.0.1 Build 1

Build Information

  • Build 1: 46.0.1-build1 0b8492c110be (ID: 20160502172042)
  • Manual - Firefox 46.0.1
    • [DONE]Regression Testing with focus on Web Compatibility, and Add-on Compatibility.
    • [DONE]Bug verification with focus on the latest fixes to land in this build.
  • Automated (configs for ondemand)
    • [DONE] Updates on release-localtest channel (report)
    • [DONE] Updates on release-cdntest channel (report)
    • [DONE] Updates on release channel (report)
    • Throttle Testing (see Walkthrough for details)
      • Used commands:
        • ./throttle.sh https://aus3.mozilla.org/update/3/Firefox/46.0/20160421124000/WINNT_x86-msvc/en-US/release/Windows_NT%206.3/default/default/update.xml
        • ./throttle.sh https://aus3.mozilla.org/update/3/Firefox/46.0/20160421124000/WINNT_x86_64-msvc/en-US/release/Windows_NT%2010.0/default/default/update.xml
        • ./throttle.sh https://aus3.mozilla.org/update/3/Firefox/46.0/20160421124000/Darwin_x86_64-gcc3-u-i386-x86_64/en-US/release/Darwin%2013.4.0/default/default/update.xml
        • ./throttle.sh https://aus3.mozilla.org/update/3/Firefox/46.0/20160421124000/Linux_x86-gcc3/en-US/release/Linux%203.13.0-45-generic%20%28GTK%202.24.23%29/default/default/update.xml
        • ./throttle.sh https://aus3.mozilla.org/update/3/Firefox/46.0/20160421124000/Linux_x86_64-gcc3/en-US/release/Linux%203.16.0-30-generic%20%28GTK%202.24.25%29/default/default/update.xml
      • Results
        • After release push (expected to be @ 25%), 2016-05-03: Win32: 23% - Win64: 26% - Mac: 24% - Linux32: 24% - Linux64: 24%
        • After disabling updates (expected to be @ 0%):
        • After fully enabling updates (expected to be @ 100%), 2016-05-05: Win32: 100% - Win64: 100% - Mac: 100% - Linux32: 100% - Linux64: 100%
Retrieved from 'https://wiki.mozilla.org/index.php?title=Releases/Firefox_46/Test_Plan&oldid=1132783'
Warning: Firefox now includes downgrade protection to prevent corruption of user profile data. If you install an older version, you'll be prompted to create a new Firefox profile.

If there is a problem with a Firefox, most people will try to revert Firefox back to the way it was before and downgrade it, but we do not recommend this action. Downgrading Firefox leaves a user more vulnerable to attacks and, on most occasions, doesn't fix the problem that occurred while updating. This article gives you some alternatives to downgrading and links to old versions of Firefox, if you do choose to downgrade.

Table of Contents

Problems with an update are generally not caused by the new version of Firefox, but rather the update process. Installing a previous version will not help in most cases. Instead, see:

Note: Other problems can be solved with the Refresh Firefox feature. It restores Firefox to its default state while saving your essential information.

Ensure all security and security related software is fully updated. Some security software will need to be upgraded to a new version for each Firefox version update.

Optional software bundled with security software may also need updating. Such software may not be essential for your security, but if outdated, it may interfere with the use of Firefox, or cause Firefox to crash.

If you want to downgrade, you can visit Mozilla's directory of older Firefox versions using the link below. Please note, however, that using older versions of Firefox can be harmful and that we recommend you use the newest version of Firefox.
Warning: Old Firefox versions pose a significant security risk.
  • Firefox 67.0.432-bit (US English)
  • Firefox 67.0.464-bit (US English)
  • Firefox 67.0.432-bit (US English)
  • Firefox 67.0.464-bit (US English)
  • Firefox 68.0.232-bit (US English)
  • Firefox 68.0.264-bit (US English)
  • Firefox 68.0.232-bit (US English)
  • Firefox 68.0.264-bit (US English)
  • Firefox 69.0.332-bit (US English)
  • Firefox 69.0.364-bit (US English)
  • Firefox 69.0.332-bit (US English)
  • Firefox 69.0.364-bit (US English)
  • Firefox 70.0.132-bit (US English)
  • Firefox 70.0.164-bit (US English)
  • Firefox 70.0.132-bit (US English)
  • Firefox 70.0.164-bit (US English)
  • Firefox 71.032-bit (US English)
  • Firefox 71.064-bit (US English)
  • Firefox 71.032-bit (US English)
  • Firefox 71.064-bit (US English)
  • Firefox 72.0.232-bit (US English)
  • Firefox 72.0.264-bit (US English)
  • Firefox 72.0.232-bit (US English)
  • Firefox 72.0.264-bit (US English)
  • Firefox 73.0.132-bit (US English)
  • Firefox 73.0.164-bit (US English)
  • Firefox 73.0.132-bit (US English)
  • Firefox 73.0.164-bit (US English)
  • Firefox 74.0.132-bit (US English)
  • Firefox 74.0.164-bit (US English)
  • Firefox 74.0.132-bit (US English)
  • Firefox 74.0.164-bit (US English)
  • Firefox 75.032-bit (US English)
  • Firefox 75.064-bit (US English)
  • Firefox 75.032-bit (US English)
  • Firefox 75.064-bit (US English)
  • Firefox 76.0.132-bit (US English)
  • Firefox 76.0.164-bit (US English)
  • Firefox 76.0.132-bit (US English)
  • Firefox 76.0.164-bit (US English)
  • Firefox 77.0.132-bit (US English)
  • Firefox 77.0.164-bit (US English)

Firefox 46 Release

  • Firefox 77.0.132-bit (US English)
  • Firefox 77.0.164-bit (US English)

Firefox 46 Free Download

  • Firefox 78.0.232-bit (US English)
  • Firefox 78.0.264-bit (US English)
  • Firefox 78.0.232-bit (US English)
  • Firefox 78.0.264-bit (US English)
  • Firefox 79.032-bit (US English)
  • Firefox 79.064-bit (US English)
  • Firefox 79.032-bit (US English)
  • Firefox 79.064-bit (US English)
Important: By default, Firefox is set for automatic updates. To prevent Firefox from automatically updating itself after you install an older version, you'll need to change your Firefox update settings: Click the menu button and select .. In the General panel, go to the Firefox Updates section.

Instead of downgrading to an older, insecure version of Firefox and changing your update settings, you should consider these alternatives:

Install Firefox Extended Support Release.Firefox Extended Support Release (ESR) is an official version of Firefox developed for large organizations like universities and businesses. Firefox ESR does not come with the latest features but it has the latest security and stability fixes. For more information, see the article Switch to Firefox Extended Support Release (ESR) for personal use.

Use the latest version of another browser. If the current Firefox version is not to your liking or just not working right now, there are alternative browsers that you can use to browse the web.

If the latest version of Firefox is causing problems for you or you just don't like something about it, please give us feedback about it here: