Confirmed users
2,473
edits
Compatibility/Mobile/WipeOutUAOverides: Difference between revisions
Jump to navigation
Jump to search
Compatibility/Mobile/WipeOutUAOverides (view source)
Revision as of 21:01, 15 April 2013
, 15 April 2013→Wipe Out User Agent (UA) Overrides
| Line 1: | Line 1: | ||
=Wipe Out User Agent (UA) Overrides= | =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== | ==Goal== | ||
| Line 7: | Line 7: | ||
===Scope=== | ===Scope=== | ||
The scope of this project is all sites listed on the [https://github.com/mozilla-b2g/gaia/blob/master/build/ua-override-prefs.js UA override list]. This list is also available in [http://mzl.la/12IPVvr Bugzilla]. | The scope of this project is all sites listed on the [https://github.com/mozilla-b2g/gaia/blob/master/build/ua-override-prefs.js UA override list]. This list is also available in [http://mzl.la/12IPVvr 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== | ==Duration== | ||