[B2G][Loop] Welcome text is not localized

RESOLVED WORKSFORME

Status

RESOLVED WORKSFORME
4 years ago
4 years ago

People

(Reporter: smiko, Unassigned)

Tracking

unspecified
ARM
Gonk (Firefox OS)

Firefox Tracking Flags

(b2g-v1.3 affected, b2g-v1.4 affected, b2g-v2.0 affected, b2g-v2.1 affected)

Details

(Whiteboard: [2.0 exploratory][not blocking])

Attachments

(1 attachment)

(Reporter)

Description

4 years ago
Created attachment 8471047 [details]
2014-08-11-14-43-58.png

Description:
When launching Loop, the welcome text is not localized

Repro Steps:
1) Update a Flame to 20140811000210
2) Install "Loop"
3) Open "Loop"

Actual:
Text is not localized

Expected:
Text is localized

Environmental Variables:
Device: Flame 2.0 (319mb)
Build ID: 20140811000210
Gaia: de28796a8956a48bb98ca67df6a33e0622d642d1
Gecko: 5256345f62bd
Version: 32.0 (2.0)
Firmware Version: v123
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0


Keywords:
Loop, text, local, welcome, screen

Repro frequency: 100%

See attached: screenshot
(Reporter)

Updated

4 years ago
Blocks: 1036490
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-v1.3: --- → affected
status-b2g-v1.4: --- → affected
status-b2g-v2.0: --- → affected
status-b2g-v2.1: --- → affected
Whiteboard: [2.0 exploratory]
(Reporter)

Comment 1

4 years ago
This issue DOES reproduce on Flame 2.1 (319mb), buri 2.1, Flame 2.0 (512mb), buri 2.0, Flame 1.4 (319mb), buri 1.4, and buri 1.3

Flame 2.1 

Environmental Variables:
Device: Flame Master
Build ID: 20140811040202
Gaia: 19ed3c9e78eaf234cc08484bde6998ae21552ba5
Gecko: a9b43778f0c2
Version: 34.0a1 (Master)
Firmware Version: v123
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

buri 2.1

Environmental Variables:
Device: Buri Master
Build ID: 20140811013006
Gaia: 19ed3c9e78eaf234cc08484bde6998ae21552ba5
Gecko: a9b43778f0c2
Version: 34.0a1 (Master)
Firmware Version: v1.2device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

Flame 2.0 (512mb)

Enviromental Variables:
Device: Flame 2.0
BuildID: 20140811000210
Gaia: de28796a8956a48bb98ca67df6a33e0622d642d1
Gecko: 5256345f62bd
Version: 32.0 (2.0)
Firmware: V123
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

buri 2.0

Environmental Variables:
Device: Buri 2.0
Build ID: 20140811063003
Gaia: 9f94a78eef3a9305140c550c983871a46b0692e7
Gecko: c2636750a6a1
Version: 32.0 (2.0)
Firmware Version: v1.2device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Flame 1.4 (319mb)

Environmental Variables:
Device: Flame 1.4
Build ID: 20140811063003
Gaia: 4a662f6dd831cf6194d7ad3501b1d56ea2964a20
Gecko: c12f198b5e51
Version: 30.0 (1.4)
Firmware Version: v123
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0

buri 1.4

Environmental Variables:
Device: Buri 1.4
Build ID: 20140811000206
Gaia: 4a662f6dd831cf6194d7ad3501b1d56ea2964a20
Gecko: e1b03b2fb92e
Version: 30.0 (1.4)
Firmware Version: v1.2device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0

buri 1.3

Environmental Variables:
Device: Buri 1.3
BuildID: 20140811024001
Gaia: 23f55be856cef53c6604a6fe4aeb09061afbc897
Gecko: ac685e277c7c
Version: 28.0 (1.3)
Firmware: v1.2device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:28.0) Gecko/28.0 Firefox/28.0
Flags: needinfo?(ktucker)
(Reporter)

Comment 2

4 years ago
The Loop application is unsupported on Flame 1.4, buri 1.4, and buri 1.3.
However, on these devices, the user is able to launch the app and view the welcome screen containing non localized text.
Should be translated but not a regression. Not nominating to block.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)

Updated

4 years ago
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][lead-review+]

Updated

4 years ago
Whiteboard: [2.0 exploratory] → [2.0 exploratory][not blocking]
This was just a 'fake' wizard, that's why the 'Lorem ipsum...' ;). Currently we have the full version working as expected. Closing as WORKSFORME.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.