Closed Bug 858734 Opened 12 years ago Closed 7 years ago

[FTU] takes a ~ 3 seconds for the UI to switch languages

Categories

(Firefox OS Graveyard :: Gaia::First Time Experience, defect, P2)

ARM
Gonk (Firefox OS)
defect

Tracking

(b2g18 affected)

RESOLVED WONTFIX
Tracking Status
b2g18 --- affected

People

(Reporter: nhirata, Unassigned)

References

Details

(Keywords: perf, Whiteboard: [c= p= s= u=])

## Environment : Master build : 2013-04-05-03-05-43 name="mozilla-central" revision="55f9e3e3dae7" name="integration/gaia-central" revision="2005e026bdae" "gecko.git" revision="66b64f47a4eac1bd4f5ea6748b42ddf732297550" "gaia.git" revision="15468abcba0dd2549f0c102df887a5c049b9c641" Unagi ## Repro : 1. run FTU 2. select a different language ## Expected : the ui will switch languages faster than ~ 3 seconds ## Actual : the ui will change in about ~ 3 seconds ## Note : Performance bug.
Whiteboard: [c= p= s= u=]
QA, Please confirm if this is still an issue on 1.2 and m-c/master. Thanks, Mike
Keywords: qawanted
QA Contact: mvaughan
Currently I am seeing languages take ~2 seconds to change... if not ~1.5 seconds. When I selected a more complicated language (e.g. Arabic) as the very first language I changed in the FTE, it would take almost 3 seconds. Either way, changing a language never took longer than 3 seconds, and on average it only took ~2 seconds on my Buri device. - 1.2 BUILD - Environmental Variables: Device: Buri v1.2 COM RIL BuildID: 20131111004004 Gaia: 670b2c8329bca6f142939185be71274166d82bb8 Gecko: 1ac147e4e2f0 Version: 26.0 RIL Version: 01.02.00.019.102 - 1.3 BUILD - Environmental Variables: Device: Buri v1.3 MOZ RIL BuildID: 20131108123740 Gaia: 01800b04cc497db9904ed8e3837187a22ebe47ee Gecko: f003c386c77a Version: 28.0a1
Keywords: qawanted
See Also: → 936726
UX Team, Any effort planned to provide more feedback during this user experience? https://wiki.mozilla.org/B2G/Performance/UserStories Product, Any guidance on perf goals for this feature?
Flags: needinfo?(firefoxos-ux-bugzilla)
Flags: needinfo?(ffos-product)
Priority: -- → P2
No benchmark defined specifically for this but We are generally targeting most user facing scenarios to take less than a second. How much of a degradation is this from prev release?
Flags: needinfo?(ffos-product)
Flagging Francis as he is on FTU, though this does seem more perf related.
Flags: needinfo?(firefoxos-ux-bugzilla) → needinfo?(fdjabri)
Re-assigning to Jacqueline, who's responsible for FTU UX.
Flags: needinfo?(fdjabri) → needinfo?(jsavory)
My first idea here (without taking a deep look to the code) is that we are expending way too much time in translating the vast DOM that is the FTU. FTU is one of the apps that still doesn't have much performance improvements and it's loading all the dom in a single page. We will be shortly involved in the splitting of the FTU app outside communications app, perhaps it's a good moment to add a bit of lazy loading of the screens and also check if we can improve this time as well.
Can you reproduce this issue on master? On April 8th we landed a major rewrite of l10n.js (bug 914414). It might have fix that.
I am currently unable to see this issue on master, but if the loading time is still too long on certain devices we can add a simple loading screen to provide some feedback to the user while switching languages.
Flags: needinfo?(jsavory)
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.