Mobile/Projects/Accept language-header: Difference between revisions

Jump to navigation Jump to search
no edit summary
(Created page with "== Goals == * == Specifications == * == User Stories == * == Tracking == <onlyinclude> <bugzilla> { "id": "881510" } </bugzilla> </onlyinclude> == Quality Criteria ...")
 
No edit summary
Line 1: Line 1:
== Goals ==
== Goals ==
*  
* To provide the ability to users to be presented and read content in their preferred language or dialect when web content is available
* This is important for users who want to interact with web content in their most comfortable and understood language
* This feature feels more important to more localized markets as well as emerging markets, where there are numerous language and dialect choices available to users, regardless of what language their phone (or Firefox) UI is set to
** For our current market focus (Q3 2013), this is not a feature requiring quick implementation - however, it is important for supporting our future plans for expanding into more localized and emerging markets where local content is key for actively engaging users with the web comfortably




== Specifications ==
== Specifications ==
*  
* If web content is available in a choice of languages, the user's chosen preferred language for presenting web content should be displayed to the user
* Must have a simple way for users to choose which is their preferred language choice for presenting web content when that choice is available, likely within one of the settings menu items
* There can be no real impact on start-up time for the browser, nor relevant impact on performance (page loads, panning, scrolling)




== User Stories ==
== User Stories ==
*  
* As a user, I want to read content in my chosen language regardless of what language is used for the Android or Firefox UI elements
* As a user, I want to easily choose which is my preferred language for displaying web content.




Confirmed users, Bureaucrats and Sysops emeriti
1,452

edits

Navigation menu