Closed Bug 1052299 Opened 6 years ago Closed 6 years ago

[b2g][l10n] SIM PIN prompt and PUK prompt are not entirely localized on 2.0

Categories

(Firefox OS Graveyard :: Gaia::System, defect)

x86_64
Linux
defect
Not set

Tracking

(blocking-b2g:2.0+, b2g-v2.0 fixed, b2g-v2.1 unaffected)

RESOLVED FIXED
2.1 S3 (29aug)
blocking-b2g 2.0+
Tracking Status
b2g-v2.0 --- fixed
b2g-v2.1 --- unaffected

People

(Reporter: angelc04, Assigned: aus)

References

Details

(Keywords: regression, Whiteboard: LocRun2.0 [systemsfe][p=1])

Attachments

(3 files)

Attached image 2014-08-12-15-58-31.png
1. Enable a SIM PIN and restart the phone.

2. When prompted to enter a SIM PIN, put in the incorrect pin 3 times.

3. Check all the strings on the "Enter PUK code" page.
   --> "Enter PUK code" page was not fully translated. But if you go back to SIm security page and try to disable PIN, the "Enter PUK code" page is fully translated.
Whiteboard: LocRun2.0
Summary: "Enter PUK code" page was not fully translated after put incorrect sim pin 3 times. → [b2g][l10n][zh-cn] "Enter PUK code" page was not fully translated after put incorrect sim pin 3 times.
(In reply to Peipei Cheng from comment #0)
> Created attachment 8471421 [details]
> 2014-08-12-15-58-31.png
> 
> 1. Enable a SIM PIN and restart the phone.
> 
> 2. When prompted to enter a SIM PIN, put in the incorrect pin 3 times.
> 
> 3. Check all the strings on the "Enter PUK code" page.
>    --> "Enter PUK code" page was not fully translated. 

But if you go back to
> SIm security page and try to disable PIN, the "Enter PUK code" page is fully
> translated.

if you lock screen and then unlock, the page become untranslated.
I cannot find the untranslated strings, could it be a i18n issue?
Théo, are you able to verify this? Not sure I have expendable SIMs around in case something goes wrong with PIN/PUK codes.
Flags: needinfo?(tchevalier)
Tried with latest 2.1 build on Flame and can't reproduce.

I suspect only 2.0 is affected (all locales), and the possible cause could be 2.0 patch from bug 1030094 not fixing the issue on 2.0 but working only on 2.1.
https://bugzilla.mozilla.org/show_bug.cgi?id=1030094#c40

Keeping needinfo, will check on 2.0 tomorrow at the office.
@Theo any updates?
Attached image Flame 2.0, fr
This is confirmed, SIM PIN prompt (not the one on FTU, the one you get when you reboot) contains en-US strings (see screenshot) on 2.0 only.


Tested with:
Gaia      295c7f50707372e5af6d8e83148d2d970076dfd6
Gecko     https://hg.mozilla.org/releases/mozilla-b2g32_v2_0/rev/879c5208084f
BuildID   20140815000200
Version   32.0
ro.build.version.incremental=110
ro.build.date=Fri Jun 27 15:57:58 CST 2014
B1TC00011230
Flags: needinfo?(tchevalier)
[Blocking Requested - why for this release]:

Since labels to create PIN/PUK codes are involved and it's the first screen seen by users, I'd ask to block on this one :/
All locales are affected.
blocking-b2g: --- → 2.0?
Summary: [b2g][l10n][zh-cn] "Enter PUK code" page was not fully translated after put incorrect sim pin 3 times. → [b2g][l10n] SIM PIN prompt and PUK prompt are not entirely localized on 2.0
PS: We have those strings, it seems that the steps-to-reproduce show a code path that doesn't pick up the strings from l10n.

Thus, this doesn't smell like late-l10n at this point.
Assignee: shaohua.wen → nobody
Component: zh-CN / Chinese (Simplified) → Gaia::System
Product: Mozilla Localizations → Firefox OS
QA Contact: shaohua.wen
Aus, Ted, if I remember correctly one of you fixed a similar bug already. Can you take a look?
blocking-b2g: 2.0? → 2.0+
Flags: needinfo?(tclancy)
Flags: needinfo?(aus)
Ah yes, this is likely caused by misuse of the l10n API. I can take a look.
Assignee: nobody → aus
Status: NEW → ASSIGNED
Flags: needinfo?(tclancy)
Flags: needinfo?(aus)
Whiteboard: LocRun2.0 → LocRun2.0 [systemsfe]
Target Milestone: --- → 2.1 S3 (29aug)
QA Contact: ckreinbring
Regression window unavailable.
Builds before the build noted below do not recognize the SIM card in either slot.

BuildID: 20140506163010
Gaia: 98ca8c55dbe2f21a8661d0eaa87f34d316c3bc98
Gecko: 4e4e0f502969
Platform Version: 32.0a1
Firmware Version: V123
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmitchell)
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell)
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][lead-review+]
This patch changes how we use the l10n api and also does an initial 'translate' of the elements. We're missing the l10n mutation observer in 2.0 and that dialog is injected dynamically, so it doesn't get translated when injected.
Attachment #8476294 - Flags: review?(gandalf)
I also double checked on 2.1 and, as expected, it all works great!
Whiteboard: LocRun2.0 [systemsfe] → LocRun2.0 [systemsfe][p=1]
Comment on attachment 8476294 [details] [review]
Pull Request - Ensure elements in SIM PIN and PUK dialog are translated.

That looks good! In 2.1 we can replace _l10n with setAttributes :) you have one unit test failing on tbpl, but except of that it's ready!
Attachment #8476294 - Flags: review?(gandalf) → review+
> That looks good! In 2.1 we can replace _l10n with setAttributes :) you have
> one unit test failing on tbpl, but except of that it's ready!

Indeed! And the code in 2.1 already uses setAttributes and relies on the mutation observer to do the rest. I'll look at that test and make sure we're all green before committing. Thanks! :)
Tests updated, green run locally, just waiting on tbpl before committing.
Test run is good (some orange factor, already known bugs).

Commit (v2.0 only): https://github.com/mozilla-b2g/gaia/commit/2e0da996317fd6bf3bb4a567ff72ce1a0428bf24

Fixed.
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.