Account confirmers, Anti-spam team, Confirmed users, Bureaucrats and Sysops emeriti
4,925
edits
B2G/User Agent/Device Model Inclusion Requirements: Difference between revisions
Jump to navigation
Jump to search
B2G/User Agent/Device Model Inclusion Requirements (view source)
Revision as of 09:11, 18 September 2013
, 18 September 2013Remove double title
(Remove double title) |
|||
| Line 1: | Line 1: | ||
Adding a device identifier to the Firefox OS User Agent (UA) string is STRONGLY DISCOURAGED by Mozilla. As studies have shown, changes to the UA string have a negative impact on web compatibility - some major websites will stop working if you do this! Further reasons are documented in the [[B2G/User_Agent/Partner_Changes_Policy|Firefox OS User Agent Partner Changes Policy]]. | Adding a device identifier to the Firefox OS User Agent (UA) string is STRONGLY DISCOURAGED by Mozilla. As studies have shown, changes to the UA string have a negative impact on web compatibility - some major websites will stop working if you do this! Further reasons are documented in the [[B2G/User_Agent/Partner_Changes_Policy|Firefox OS User Agent Partner Changes Policy]]. | ||
| Line 13: | Line 11: | ||
==Specific requirements for the device identifier ("XXXX")== | ==Specific requirements for the device identifier ("XXXX")== | ||
# Use a simple token. For example, "NexusOne" or "ZTEOpen". Do not use slash ("/"), semicolon (";"), round brackets or any whitespace. It is recommended that you use only letters (“A-Za-z”), numbers (“0-9”), hyphen (“-”) and dot (“.”). Shorter is better.<br | # Use a simple token. For example, "NexusOne" or "ZTEOpen". Do not use slash ("/"), semicolon (";"), round brackets or any whitespace. It is recommended that you use only letters (“A-Za-z”), numbers (“0-9”), hyphen (“-”) and dot (“.”). Shorter is better.<br><br> | ||
# The device model identifier should always be the same for a particular device, and should stay the same for a successor or sibling device unless the hardware configuration is different in a way relevant to the web (i.e. not just a different chipset). Indicate the difference between devices with the same brand name but different hardware configurations using a more complete name, such as “HTCOne”, “HTCOneX”, and “HTCOneXPlus”, or a numeric identifier such as “ZTEOpen”, “ZTEOpen2”, and “ZTEOpen3”. Remember that this string is not user-visible so does not need to match your branding strategy.<br | # The device model identifier should always be the same for a particular device, and should stay the same for a successor or sibling device unless the hardware configuration is different in a way relevant to the web (i.e. not just a different chipset). Indicate the difference between devices with the same brand name but different hardware configurations using a more complete name, such as “HTCOne”, “HTCOneX”, and “HTCOneXPlus”, or a numeric identifier such as “ZTEOpen”, “ZTEOpen2”, and “ZTEOpen3”. Remember that this string is not user-visible so does not need to match your branding strategy.<br><br> | ||
# Do not include a "build id" in addition to the device name. This will simply damage web compatibility. | # Do not include a "build id" in addition to the device name. This will simply damage web compatibility. | ||