This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
We need a final list of mobile browsers for compat. tables at launch. See also: https://www.w3.org/Bugs/Public/show_bug.cgi?id=19129 https://www.w3.org/Bugs/Public/show_bug.cgi?id=19130 https://www.w3.org/Bugs/Public/show_bug.cgi?id=19131
*** Bug 19129 has been marked as a duplicate of this bug. ***
*** Bug 19130 has been marked as a duplicate of this bug. ***
*** Bug 19131 has been marked as a duplicate of this bug. ***
Mobile browser list created OLD Android Support Android Support (prefixed) Firefox Mobile Support Firefox Mobile Support (prefixed) IE Phone Support IE Phone Support (prefixed) Opera Mobile Support Opera Mobile Support (prefixed) Safari Mobile Support Safari Mobile Support (prefixed) NEW Android support Android support (prefixed) Blackberry support Blackberry support (prefixed) Chrome for mobile support Chrome for mobile support (prefixed) Firefox for mobile support Firefox mobile support (prefixed) Internet Explorer Mobile support Internet Explorer Mobile support (prefixed) Opera Mobile support Opera Mobile support (prefixed) Opera Mini support Opera Mini support (prefixed) Safari for iOS support Safari for iOS support (prefixed) The Unknown/No/Yes system works pretty well, as does entering a specific version number only if you have it. I think we should add functionality for people to just add a new row to the compat table, if they want to add another browser in. I think the browsers I have listed are representative of a general worldwide view, although in some countries other specific browsers are very big, like Baidu and UCWeb in China (same with Maxthon on desktop). Rather than adding all of these browsers, we should probably just give interested parties the opportunity to add their own compat info.
This needs to be implemented in the templates and forms. Note that the ability for folks to add new browsers to the compatibility table is non-trivial to implement in MediaWiki templates.
(In reply to comment #5) > This needs to be implemented in the templates and forms. > > Note that the ability for folks to add new browsers to the compatibility table > is non-trivial to implement in MediaWiki templates. Ok, for now let's just implement my list then, and then think about adding other browsers if there is great demand. For example, it might make sense to have browsers like UCWeb and Baidu listed on Chinese translations only? But I'm not 100% sure.
Some additional thoughts: if we only have a fixed number of supported browsers, which we probably should to prevent forever expanding table, then we need to add to the FAQ the policy and reasoning. I think it is fair to suggest webplatform.org is not specializing in test/compatibility. There are specialized websites, caniuse.com, http://mobilehtml5.org/ or http://www.quirksmode.org/mobile/. We can also create an articles to list these websites, say About mobile testing and compatibility resources etc. Thx.
I've implemented this in templates, although I think Wai's comment is a good one to address.
(In reply to comment #8) > I've implemented this in templates, although I think Wai's comment is a good > one to address. I have added an entry to the FAQ to cover this: see the bottom of http://docs.webplatform.org/wiki/WPD:FAQ