Hi QA Community!
Once again, warm greetings to all of our great community testers – you
are our most valuable resource. We now have Firefox 4 Beta 11 available
for testing. Note that this build is a development build and is intended
for pre-release testing. We would like your help in testing the build
and identifying any possible regressions or issues. You can read all
about the release here: http://www.mozilla.com/en-US/firefox/beta/
What to Test/Where to Get Builds:
*Please see http://www.mozilla.com/en-US/firefox/all-beta.html – there
are direct links to the builds on that page.
Please hammer on these builds mercilessly to make sure that things work
Read the Release Notes
* Please also make sure to read the which detail the known issues and
describe the complete list of changes in this version. You can find the
Release Notes here –
*Some cool things to try:
** Windows 7 Users only: Try out the sites listed at the bottom of this
** Try out Firefox Panorama!
** Try out Firefox Sync! Sync to your Android or iPhone!
** Try out the Feedback button!
** Make sure to go to Mozilla Plugin Check
http://www.mozilla.com/en-US/plugincheck/ to verify you are running the
latest version of Flash and other plugins.
** Explore some other focus areas:
With the integration of the “Do Not Track” option into Firefox 4 Beta
11, you can now check a “Do Not Track” box in the “Advanced” screen of
Firefox’s Options. When this option is selected, a header will be sent
signaling to websites that you wish to opt-out of online behavioral
tracking. You will not notice any difference in your browsing experience
until sites and advertisers start responding to the header.
You can read more about behavioral tracking in this post
from Mozilla Privacy Lead, Alex Fowler. For more information about the
technical implementation Do Not Track, check out this post
from Sid Stamm, Mozilla security and privacy engineer.
How to Report Feedback:
(1) File a bug in Bugzilla. *Note in the comment if it is a regression
from a previous release. Things to remember when filing a bug:
(a) Always include the Build ID that you tested on. If you type about:
in the URL bar, this will give you the Build ID.
(b) Always include clear Steps to Reproduce the bug
(c) Always check to see if your bug has already been filed.
(d) Use the regression keyword if it indeed a regression from a previous
(e) If you happen to crash, please submit your crash information! This
helps us continually improve the product. Please also include the
Breakpad Crash ID in the bug. You can get the crash ID by typing
about:crashes in the URL bar.
(f) If you tend to run with lots of extensions, try starting Firefox in
Safe Mode before filing to bug to see if the problem persists.
(2) If you don’t wish to file a bug, report issues through the Firefox
Feedback button, http://feedback.mozilla.org or through the
mozilla.feedback.firefox.prerelease newsgroup (also available on Google
Groups). However, we prefer bugs as feedback is easier to track.
Thanks in advance to all of you for helping test Firefox and making it
the browser of choice for millions of people all over the world!
Team Mozilla QA