Our goal, is to open up the Web to all mobile browsers via promotion of standards and best practices.
However, some websites serve content either that doesn't function well or that is different than that served to some specific popular mobile browsers of the moment. This content may be:
- A basic mobile site
- A traditional desktop site
- A WAP (Wireless Application Protocol) site designed for a feature phone
- A touch-optimized mobile site that is broken visibly or functionally
We refer to this category of issues as Web compatibility issues. Web compatibility issues (for Firefox for Android, Firefox OS and other browsers with limited market share in one or more regions) typically result from one or more of several causes:
- User-agent sniffing
- Identifying the browser by its user-agent string and sending different content.
- Use of non standard (typically Webkit) CSS properties
- Using non standard CSS properties that the browser does not recognize, causing layout or style issues
- Use of non standard (typically Webkit) DOM properties
- Browser limitations
- Using standard CSS and DOM properties that the browser does not currently implement or that have functional or performance issues
For Firefox specifically, we need your help to identify sites that do not work well by reporting the specific issues that you find in your investigation. Other browsers vendors have bug reporting systems, where you can report the issues as well for their specific browser.
Outlined below are steps that you can follow to identify and report site issues.
To start, let's set up your hardware and software for compatibility testing.
- An Android phone is a prerequisite for testing Firefox for Android. See our list of supported devices for Firefox for Android to ensure that your phone is supported.
- Install Firefox for Android from Google Play.
- Install the Phony Add-on for Firefox on Android. This add-on lets Firefox for Android pretend to be another browser by changing the user-agent string that is sent with each HTTP request.
- Set up an account on bugzilla so that you can report issues.
- Install Firefox for Android for a different release channel: Beta, Aurora, or Nightly.
- You can try to reproduce and debug issues that you discover in Desktop Firefox. Install Desktop Firefox for Windows, Linux or Mac OS X and an add-on like Phony for the desktop.
Note: See the article Browser detection using the user agent for an in-depth explanation about browser user-agents.
The following steps walk you through the method that Mozilla QA uses for compatibility testing:
- Select a site to test.
- This may be a site that you already visited and saw that something is wrong in your daily browser usage.
- Alternatively, you can select one of the top sites listed on the Are We Compatible Yet report. Sites that have not yet been investigated are shown in white.
- Open the site that you selected in Firefox for Android. Test the functionality of the site by exploring different areas of the site. For example, if the site displays articles, pictures, and videos, you should explore all three areas of the site. Click on links, use forms, create accounts, sign in, and question:
- Is the site a desktop site? If so, skip to #3 and #4 to determine if Safari on iPhone and the Android browser are served the same desktop content.
- Does the site have obvious layout problems? Are elements positioned on top of one another? Is there missing content? Do menus display correctly? Are header background colors correct? Are areas of the page shown correctly? Does the site simply look bad?
- Visit the same website using your device’s Android browser, using the same exploration methods in #2, and question:
- Is the site a desktop site? Does the content greatly differ than what you saw on Firefox for Android? If so, how is it different? Is it a mobile optimized site?
- Are there any similar layout issues as seen in Firefox for Android? If so, what problems do you see with Firefox for Android that you do not see in the Android browser?
- Make Firefox for Android appear to the site as though it is Safari on iPhone by clicking Menu->Phony and selecting iPhone. After selecting iPhone click Menu->Reload. Visit the same site again and continue with the same exploration methods in #2 and question:
- Is the site a desktop site? Does the content greatly differ than what you previously saw in Firefox for Android? If so, how is it different? Is it a mobile optimized site?
- Does the site have any layout problems? If so, what are those problems?
For any site that looks or functions differently in Firefox for Android, the Android browser, or Safari on iPhone you should report each issue in Bugzilla. To report an issue, file a bug in the Firefox for Android Evangelism component and provide as much information about the issue as you can. Here are some pieces of information that are typically helpful to submit with your report:
- Summarize the issue that you have identified with the site. It is helpful to include the domain name, such as mozilla.org, in the summary.
Describe the issue as best as you can. Include details such as how the content differs between Firefox for Android, Android browser, and Safari on iPhone, the specific places (titles, article list, options menu) where the site does not look correct, and what parts of the site (articles are unreadable, videos don't play, can't click on links) that do not function as you expected that they would.
- It is also valuable to attach a screen capture that shows the problem in Firefox for Android. How to take a screenshot on Android differs based on your version of the operating system.
If you have any questions about compatibility testing or want to become involved in Mozilla’s mobile web compatibility effort, please sign up for the firstname.lastname@example.org mailing list.