Account confirmers, Anti-spam team, Confirmed users, Bureaucrats and Sysops emeriti
4,925
edits
B2G/User Agent/Partner Changes Policy: Difference between revisions
Jump to navigation
Jump to search
B2G/User Agent/Partner Changes Policy (view source)
Revision as of 14:07, 14 June 2013
, 14 June 2013no edit summary
No edit summary |
No edit summary |
||
| Line 60: | Line 60: | ||
It is impractical to think that the mobile Web can be "fixed" in the short term. In support of the Firefox OS user experience, Firefox OS has the capability to send a custom UA to a specific site in order to force mobile content. Often the change is simply to include the "Android" token in the UA, thus masquerading Firefox OS as Firefox for Android. The process for adding a site to the UA override list is [[Evangelism/UA_Override_List_Policy|documented on the Mozilla wiki]]. Mozilla has already added certain sites to the list which are important in Firefox OS launch markets. Mozilla permits partners to add a reasonable number of other individual sites to the list after confirming that doing so will result in an improved user experience. We strongly recommend that partners not to rely on the UA override list as a long term solution and encourage them to open a dialogue about moving to a more future-proof model of capability detection with each site on the list. | It is impractical to think that the mobile Web can be "fixed" in the short term. In support of the Firefox OS user experience, Firefox OS has the capability to send a custom UA to a specific site in order to force mobile content. Often the change is simply to include the "Android" token in the UA, thus masquerading Firefox OS as Firefox for Android. The process for adding a site to the UA override list is [[Evangelism/UA_Override_List_Policy|documented on the Mozilla wiki]]. Mozilla has already added certain sites to the list which are important in Firefox OS launch markets. Mozilla permits partners to add a reasonable number of other individual sites to the list after confirming that doing so will result in an improved user experience. We strongly recommend that partners not to rely on the UA override list as a long term solution and encourage them to open a dialogue about moving to a more future-proof model of capability detection with each site on the list. | ||
==Alternatives== | |||
One use of putting e.g. a device identifier in the UA is to look up information about the device (e.g. screen size) in a server-side database. However, this method fails when a device is not in the database, or not in the version the site is using. Mozilla recommends that the best way to find this information is simply to ask the device at the time the user visits the site or uses the app. Properties like screen size are available through JavaScript. | |||
<!-- | <!-- | ||
==Resources== | ==Resources== | ||