Mobile/Evangelism/Taxonomy

	THIS PAGE IS A WORKING DRAFT
	The page may be difficult to navigate, and some information on its subject might be incomplete and/or evolving rapidly. If you have any questions or ideas, please add them as a new topic on the discussion page.

This page will attempt to enumerate the various challenges non-webkit browsers face.

Desktop page when Stock has a mobile specific page

Likely user agent sniffing or lack of sniffing

Mobile feature phone site

Likely bad user agent sniffing

Mobile frameworks

There are several mobile frameworks that use the verbose user agents and http headers to do phone specific feature detection. Mozilla does not see sending this info as a way to fix this problem as Firefox mobile can support features that the stock browser does not and vice versa.

Webkit CSS

This is CSS that is still in the process of being spec'ed by the CSSWG and implemented by browser vendors. Since a majority of the new mobile browsers are Webkit based it is common to see mobile sites write CSS using Webkit specific rules such as -webkit-border-radius without corresponding non-prefixed, -moz, -ms, or -o variants.

wap mime-type

Page is served with the mime type "application/vnd.wap.xhtml+xml" bug 209637