Compatibility/Mobile/WipeOutUAOverides

Wipe Out User Agent (UA) Overrides

User Agent (UA) overrides were added to B2G for sites that were determined to be important to the user experience that were not sending B2G mobile content. The UA overrides were added using the platform's UA override mechanism, which provides the facility to request mobile content when the B2G UA is not recognized as mobile. This UA override mechanism is to be a short lived solution until the Web content is fixed to recognize B2G as mobile.

Goal

This goal of this project is to drive the B2G UA override list to zero.

Scope

The scope of this project is all sites listed on the UA override list. This list is also available in Bugzilla.

The sites for which UA overrides have been added have each been smoke tested to ensure that they are functional. The request of these sites is simply to recognize the B2G UA as mobile, preferably by recognizing the "Mobi" token in the UA.

Note: Mozilla recommends the use of responsive design and feature detection over UA detection. The request to augment a site to use these methods is much greater than the request to modify the existing site UA detection logic. This makes requesting the recognition of the B2G UA the lowest bar to 'fixing' these sites.

Duration

TBD

Communication

Communication Type	Mechanism	Audience
UA override list	Gaia source file, Bugzilla bugs	All

Press & Blog Posts

• Lawrence Mandel: Help Wanted: Firefox OS UA Detection

Progress Reports

2013
reports go here

People

Project Management	Lawrence Mandel
Partner Outreach	Karl Dubost
Tooling	Hallvord Steen

UA Override List

Outstanding

No results.

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

Fixed

No results.

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

Updating the UA override list

Once a bug has been resolved it is necessary to update the ua-override list on the gaia project. It is possible to make one pull request for a few ua strings override at the same time.

For the following instructions, you are expected to have

1. A github account
2. A working knowledge of git
3. A Mozilla bugzilla account

These steps are done once and for all.

1. Go to Gaia project on github.
2. Fork it
   https://github.com/{your_account}/gaia/
3. Clone the project locally on your computer. It will be long. it's >300Mo
   git clone https://github.com/{your_account}/gaia/
cd gaia
4. Add the project as an upstream to help you keep in sync.
   git remote add upstream https://github.com/mozilla-b2g/gaia.git

Each time you have to modify the list :)

1. Synchronize your repo with the mother repo
   git fetch upstream
2. Modify the gaia/blob/master/build/ua-override-prefs.js
3. Do a commit for the modification
   commit -m "bug_number - bug label" ua-override-prefs.js
4. You can create a diff file for a patch if you want. Not mandatory.
   git diff -U8 > ~/ua-override-prefs-YYYYMMDD.patch you might want to add it to the bug you will create later on.
5. Create a new bug in bugzilla with the title "Remove UA override for example.org". Replace example.org by the domain or list of domains.
6. Product: Boot2Gecko, Component: Gaia, Platform: ARM, Gonk (Firefox OS)
7. Add the Patch as an attachment.
8. One finished, push your modification to your github repo.
   git push
9. Create a pull request in your github repo for the gaia project with your modifications. Important: Pull request syntax title is precise Bug bug_number - Remove UA override for [list of domains] The bug_number is the one given by bugzilla you just created. It needs to start by Bug.
10. Add a comment on the bugzilla with the link to the new created Pull Request.
11. Ask for review in bugzilla and put lmandel for reviewer with a "?"
12. When review is done, adding the checkin-needed keyword on the bugzilla
13. Add a dependency on bug 890004