Mozilla Firefox 48.0

Mozilla Firefox 48.0.2 32 Bit
Mozilla Firefox 48.0 32-bit Download
Mozilla Firefox 56.0.2
Mozilla Firefox 48.0.2 64 Bit Download
Mozilla Firefox 48.0 Download
Mozilla Firefox 55.0.3 X64 En Us Download

Mozilla Firefox is a fast, light and tidy open source web browser. At its public launch in 2004 Mozilla Firefox was the first browser to challenge Microsoft Internet Explorer’s dominance. Since then, Mozilla Firefox has consistently featured in the top 3 most popular browsers globally and this is set to continue thanks to the release of. To install Firefox on a Windows XP system, because of Windows restrictions, the user will have to download Firefox 43.0.1 and then update to the current release. Recommended Hardware Pentium 4 or newer processor that supports SSE2. Mozilla Firefox 48.0 voor Windows (64bit, Engels) Mozilla Firefox 48.0 voor Linux (32bit, Engels) Mozilla Firefox 48.0 voor Linux (64bit, Engels) Mozilla Firefox 48.0 voor OS X (Engels) Mozilla. Firefox for Android Release August 2, 2016 Version 48.0, first offered to Release channel users on August 2, 2016 We'd also like to extend a special thank you to all of the new Mozillians who contributed to this release of Firefox! Advanced SystemCare uses a one-click approach to clean, optimize, speed up, and protect your computer. Get rid of junk files, protect your privacy, clean your registry, undelete files, and more.

Easier Browsing

Mozilla put of a lot of resources into creating a simple but effective UI aimed at making browsing quicker and easier. They created the tab structure that has been adopted by most other browsers. In recent years Mozilla has also focused on maximizing browsing area by simplifying toolbar controls to just a Firefox button (which contains settings and options) and back/forward buttons. The URL box features direct Google searching as well as an auto predict/history feature called Awesome Bar. On the right side of the URL box there are bookmarking, history and refresh buttons. To the right of the URL box is a search box which allows you to customize your search engine options. Outside of that a view button controls what you see below the URL. Next to that you have the download history and home buttons.

Speed

Mozilla Firefox boasts impressive page load speeds thanks to the excellent JagerMonkey JavaScript engine. Start up speed and graphics rendering are also among the quickest in the market. Firefox manages complex video and web content using layer-based Direct2D and Driect3D graphics systems. Crash protection ensures only the plugin causing the issue stops working, not the rest of the content being browsed. Reloading the page restarts any affected plugins. The tab system and Awesome Bar have been streamlined to launch/get results very quickly too.

Security

Firefox was the first browser to introduce a private browsing feature which allows you to use the internet more anonymously and securely. History, searches, passwords, downloads, cookies and cached content are all removed on shutdown. Minimizing the chances of another user stealing your identity or finding confidential information. Content security, anti-phishing technology and antivirus/antimalware integration ensures your browsing experience is as safe as possible.

Download: Mozilla Firefox 48.0.2 64-bit (32-bit)

< Releases

1Summary
- 1.6QA Activities
2Milestones
- 2.2Betas
  - 2.2.1Beta 1
  - 2.2.2Beta 2
  - 2.2.3Beta 3
  - 2.2.4Beta 4
  - 2.2.5Beta 5
  - 2.2.6Beta 6
  - 2.2.7Beta 7
  - 2.2.9Beta 9
  - 2.2.10Beta 10
- 2.3Release Candidates
  - 2.3.148.0 RC
  - 2.3.248.0 RC2
  - 2.3.3Release 48.0
  - 2.3.448.0.1 Build 1
  - 2.3.548.0.1 Build 3
  - 2.3.648.0.2 Build 1

This page is to track testing of Firefox 48 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

Please consult the Rapid Release Calendar for more information.

Milestone	Date	Checks
Nightly	2016-03-07	Conduct daily stability and bug triage, ensure features are owned
Aurora Migration	2016-04-18	Conduct testing to ensure Firefox 48 Aurora builds are okay, sign off for updates on Friday
Aurora Updates enabled	2016-04-22	Continue daily stability and bug triage, ensure features are tested
Beta Uplift	2016-06-06	Review testing and sign off every beta release
Release	2016-08-02	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 & Thursday	ReleaseCoordination	#planning
Firefox QA	Meet the Desktop QA team and hear what they're working on	8:30am Pacific on Wednesdays	DesktopQA	#qa
QA Team	Meet the entire QA team and hear what they're working on!	1:30am Pacific on Wednesdays	QA	#qa

Nightly

During the 6 weeks that Firefox 48 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 48:
Bugs fixed / verified on 48:
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 48 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

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 48.1, all bugs: https://bugzilla.mozilla.org/buglist.cgi?f1=OP&j1=OR&f2=cf_fx_iteration&o2=substring&v2=48.1&f3=status_whiteboard&o3=substring&v3=s%3D48.1&f4=CP
Iteration 48.2, all bugs: https://bugzilla.mozilla.org/buglist.cgi?f1=OP&j1=OR&f2=cf_fx_iteration&o2=substring&v2=48.2&f3=status_whiteboard&o3=substring&v3=s%3D48.2&f4=CP
Iteration 48.3, all bugs: https://bugzilla.mozilla.org/buglist.cgi?f1=OP&j1=OR&f2=cf_fx_iteration&o2=substring&v2=48.3&f3=status_whiteboard&o3=substring&v3=s%3D48.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

Betas

Beta 1

Build Information