Confirmed users
2,473
edits
B2G/User Agent/Partner Changes Policy: Difference between revisions
no edit summary
No edit summary |
|||
| Line 18: | Line 18: | ||
For sites that cannot adapt in the short term, Firefox OS includes a [[#Short_term_work-around|short term work-around]] that can be enabled on a per-site basis. | For sites that cannot adapt in the short term, Firefox OS includes a [[#Short_term_work-around|short term work-around]] that can be enabled on a per-site basis. | ||
<!-- | |||
This document includes a list of [[#Resources|resources]] for testing sites, and documentation about alternative methods to UA detection. | This document includes a list of [[#Resources|resources]] for testing sites, and documentation about alternative methods to UA detection. | ||
--> | |||
==Pragmatic reasons for not modifying the Firefox OS UA== | ==Pragmatic reasons for not modifying the Firefox OS UA== | ||
| Line 60: | Line 61: | ||
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. | ||
<!-- | |||
==Resources== | ==Resources== | ||
| Line 70: | Line 71: | ||
XXX | XXX | ||
--> | |||