Testing Top Sites for Mobile Gecko Compatibility
Many top sites today on the web are serving Firefox for Android inferior (in-comparison to content served to other widely used mobile browser) mobile sites, traditional desktop sites, WAP (Wireless Application Protocol) or sites with functional and layout issues. These areas of contention arise due to:
- Sniffing the target browser’s user agent to send differing content to Firefox for Android in-comparison to other mobile browsers
- Usage of targeting WebKit based prefixes in CSS styling when serving a site on Firefox for Android
We need your help in identifying which top sites are having problems and what problems those sites are having. We are largely focused on getting standardized compliant mobile content.
Outlined below are steps to help one understand how to identify site problems and how one might report them.
2. Setup Steps
The following steps tell one what one needs in order to help test top sites for mobile-oriented Gecko compatibility:
- Own a phone that is in our list of supported devices for Firefox for Android (http://www.mozilla.org/en-US/firefox/mobile/platforms/)
- Install Firefox for Android off of Google Play (https://play.google.com/store/apps/details?id=org.mozilla.firefox)
- Install the Phony Add-on (a user-agent switcher) for Firefox on Android
- Setup an account on bugzilla here
Optional step: Install Firefox for Windows, Linux or Mac OS X alongside a user-agent switcher (see this article for an in-depth explanation about browser user-agents) to assist in further exploratory investigation into site differing issues.
3. Testing Steps
The following steps illustrates how one might test a top site after completion of the aforementioned setup instructions detailed in section 2:
- Select a top site to test off of this list here that is flagged for investigation
- Visit the selected website in Firefox for Android  and begin with exploration. Test the functionality of the site by visiting different areas of the site. Click on links, use forms, create accounts, sign-in, and question:
- Does the site have any blatant layout problems? Are elements overlapped? Is there missing content? Are areas of the page not shown correctly? Does the site simply look bad?
- Is the site a desktop site? Is the site exactly the same as one might see it on desktop? Are the URL’s the exact same? Is the site the same site that one would get with the iPhone user agent? Android Browser user agent? Opera user agent? Chrome user agent? Desktop Firefox user-agent. Feel free to explore by testing the same website in Firefox for Windows, Linux or Mac OS X and compare to what one might see on an Android device.
- Visit the same website on the device’s Android Browser and begin with the same exploration methods, and question:
- Are there any similar layout issues as seen in Firefox for Android? If so, what problems do you see on Firefox for Android that do not show up in the Android Browser?
- Does the site render as a mobile site? Does the content greatly differ than what was seen on Firefox for Android?
- On Firefox for Android, switch the user agent to IPhone using the Phony add-on. Visit the same website again and continue with the same exploration methods and question:
- Is the site rendered different than what was seen on 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?
 Firefox for Android sends the following user agents to sites:
- Phone: Mozilla/5.0 (Android; Mobile; rv:14.0) Gecko/14.0 Firefox/14.0:
- Tablet: Mozilla/5.0 (Android; Tablet; rv:14.0) Gecko/14.0 Firefox/14.0
4. Reporting Results
If you find out that the Android Browser or iPhone user agent appear to have been served better (differing for better or worse) mobile optimized content with less layout problems than Firefox for Android, then you should report those problems in Bugzilla.
To file a bug on a problem you found while testing, file a bug in the Fennec Native Evangelism component in Bugzilla and provide the following information that may provide useful in investigation:
- Component: Set this to Evangelism
- Summary: Provide a short summary of the problem you found on a certain site
- Description: Provide a description summarizing the problem including details such as what is seen in Firefox for Android, what is seen in the Android Browser, and lastly what is seen with the IPhone user agent. Please also include a summary of the underlying problems
It is also valuable to attach to the bug to be filed a screen capture that identifies and exposes the problem in Firefox for Android from one's Android device. More information on how might one create an Android screen capture can be read here.
5. Contact Information
If you have any questions on how to test, become engaged in our evangelism process, or comment and question on anything about Mozilla’s mobile website compatibility efforts, feel free to send an email to: email@example.com.