Closed
Bug 863778
Opened 11 years ago
Closed 11 years ago
Incorrect message content (in application) and missed SIM icon (in widget) when launching Usage without a SIM
Categories
(Firefox OS Graveyard :: Gaia::Cost Control, defect)
Tracking
(blocking-b2g:leo+, b2g18+ fixed)
RESOLVED
FIXED
blocking-b2g | leo+ |
People
(Reporter: davehunt, Assigned: salva)
References
()
Details
Attachments
(2 files, 1 obsolete file)
Steps to reproduce: 1. Remove SIM from device and restart 2. Unlock device and launch Usage application Expected message: No SIM inserted Insert a SIM to enable Usage Actual message: widget-no-sim2-heading widget-no-sim2-meta Build identifier: 20130415230205 Gecko revision: 2e24a451e0a50a5896570e628ce4a49810da49a7 Gaia revision: c614b3f3c956dc1e1adf93cf4cf41511ce75de80 Using build from: https://pvtbuilds.mozilla.org/pub/mozilla.org/b2g/nightly/mozilla-b2g18-unagi-eng/2013/04/2013-04-12-07-02-04/
Reporter | ||
Comment 1•11 years ago
|
||
My gecko/gaia revisions were inaccurate in comment 0. Here is the result of my bisect: Last good: Gecko revision: 2e24a451e0a50a5896570e628ce4a49810da49a7 Gaia revision: c614b3f3c956dc1e1adf93cf4cf41511ce75de80 https://pvtbuilds.mozilla.org/pub/mozilla.org/b2g/nightly/mozilla-b2g18-unagi-eng/2013/04/2013-04-10-07-02-09/ First bad: Gecko revision: db16b691fbdd26b9c08ea2a7ba8b1025a7cbf037 Gaia revision: 6992012da593f4ce413a57e53aff64babdb5a94f https://pvtbuilds.mozilla.org/pub/mozilla.org/b2g/nightly/mozilla-b2g18-unagi-eng/2013/04/2013-04-10-23-02-04/
Reporter | ||
Comment 2•11 years ago
|
||
My guess would be this: https://github.com/mozilla-b2g/gaia/commit/1d6bfba06bb54688466a980d165741470d0c13a4
Reporter | ||
Comment 3•11 years ago
|
||
I noticed this in the logcat: E/GeckoConsole( 530): Content JS WARN at app://costcontrol.gaiamobile.org/gaia_build_defer_index.js:1 in consoleWarn: [l10n] #widget-no-sim2-heading is undefined. E/GeckoConsole( 530): Content JS WARN at app://costcontrol.gaiamobile.org/gaia_build_defer_index.js:1 in consoleWarn: [l10n] #widget-no-sim2-meta is undefined.
Reporter | ||
Updated•11 years ago
|
blocking-b2g: --- → tef?
Reporter | ||
Updated•11 years ago
|
blocking-b2g: tef? → leo?
Comment 4•11 years ago
|
||
This looks like a simple fix and a nice user win.
blocking-b2g: leo? → leo+
status-b2g18:
--- → affected
Updated•11 years ago
|
Assignee: nobody → evanxd
Comment 5•11 years ago
|
||
Hi all, I knew the root cause. We showed the locales message(#widget-no-sim2-heading, #widget-no-sim2-meta) before the localized event was triggered. So these locales messages were undefined.
Comment 6•11 years ago
|
||
Hi Salvador, Please help me review the patch. Thanks. :)
Attachment #741658 -
Flags: review?(salva)
Assignee | ||
Comment 7•11 years ago
|
||
Comment on attachment 741658 [details] Pointer to GitHub pull request: https://github.com/mozilla-b2g/gaia/pull/9396 If you do that, then every time the language is changed the application will be re-initialized. There are some tricky details as well (a missing image, some initialization issues...) so let me steal the bug.
Attachment #741658 -
Flags: review?(salva) → review-
Assignee | ||
Updated•11 years ago
|
Assignee: evanxd → salva
Assignee | ||
Updated•11 years ago
|
Summary: Incorrect message content when launching Usage without a SIM → Incorrect message content (in application) and missed SIM icon (in widget) when launching Usage without a SIM
Assignee | ||
Comment 8•11 years ago
|
||
Attachment #741658 -
Attachment is obsolete: true
Attachment #741965 -
Flags: review?(francisco.jordano)
Assignee | ||
Updated•11 years ago
|
blocking-b2g: leo+ → tef?
Assignee | ||
Comment 9•11 years ago
|
||
Mmmm, this is not reproducing on v1.0.1 but I was pretty sure it could happen. Returning to leo?
blocking-b2g: tef? → leo?
tracking-b2g18:
--- → ?
Comment 10•11 years ago
|
||
Getting back to leo+ based on comment #4 & since it looks like a regression.
blocking-b2g: leo? → leo+
Comment 11•11 years ago
|
||
Hi Salvador, Cool! I learned it. Thanks. :)
Assignee | ||
Comment 12•11 years ago
|
||
Thank you for spotting it out.
Comment 13•11 years ago
|
||
No problem. :)
Updated•11 years ago
|
Comment 14•11 years ago
|
||
Comment on attachment 741965 [details]
L10n issues solved and missing icon recovered
r+ once addressed the small comment on github.
As you all commented, easy win for the user
Attachment #741965 -
Flags: review?(francisco.jordano) → review+
Assignee | ||
Comment 15•11 years ago
|
||
Master: e9ddc19b350c11349914f0241357780fe884cc73
Assignee | ||
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Comment 16•11 years ago
|
||
I was not able to uplift this bug to v1-train. If this bug has dependencies which are not marked in this bug, please comment on this bug. If this bug depends on patches that aren't approved for v1-train, we need to re-evaluate the approval. Otherwise, if this is just a merge conflict, you might be able to resolve it with: git checkout v1-train git cherry-pick -x -m1 e9ddc19b350c11349914f0241357780fe884cc73 <RESOLVE MERGE CONFLICTS> git commit
Assignee | ||
Comment 17•11 years ago
|
||
This bug depends on (in this order): * Bug 841294 - this does not apply cleanly but it's easy to merge * Bug 859898 - apply cleanly (asking for approval-gaia) * Bug 862421 - apply cleanly (asking for approval-gaia) Once the dependencies were landed, this patch will apply cleanly.
Assignee | ||
Updated•11 years ago
|
Flags: needinfo?(jhford)
Comment 18•11 years ago
|
||
841294 will not be uplifted to v1-train 859898 is not yet approved for v1-train 862421 is not yet approved for v1-train It looks like we either need to revisit the decision to not uplift 841294 or we need to rework this patch to apply on v1-train.
Flags: needinfo?(jhford) → needinfo?(salva)
Assignee | ||
Comment 19•11 years ago
|
||
Despite it is no my deccision if bug 841294 should be uplifted or not, I recommend it since the code was tested and reviewed and we are only blocking in a l10n issue even Stas recommend us no to blocking on it [1]. We can open a follow up bug to change the key and land both of them on v1-train or we can open a follow up to remove the dot. [1] https://bugzilla.mozilla.org/show_bug.cgi?id=841294#c9
Flags: needinfo?(salva)
Assignee | ||
Updated•11 years ago
|
Flags: needinfo?(jhford)
Comment 20•11 years ago
|
||
Uplifting this without the tests that depend on a feature that'll not be uplifted seems logical to me, but I'd like to get confirmation that from leo+'er. Bhavana, what are your thoughts on the risk of uplifting this without the tests?
Flags: needinfo?(jhford) → needinfo?(bbajaj)
Comment 21•11 years ago
|
||
(In reply to John Ford [:jhford] -- If you expect a reply from me, use needsinfo? instead of CC from comment #20) > Uplifting this without the tests that depend on a feature that'll not be > uplifted seems logical to me, but I'd like to get confirmation that from > leo+'er. > > Bhavana, what are your thoughts on the risk of uplifting this without the > tests? sorry, this was for the wrong bug!
Flags: needinfo?(bbajaj)
Assignee | ||
Comment 22•11 years ago
|
||
After landing all dependencies, this applies cleanly. Thank you guys! v1-train: 25c80bc0acb1b6b541b3c5c07d8e2301f0d85c8d
Assignee | ||
Comment 23•11 years ago
|
||
(In reply to Salvador de la Puente González [:salva] from comment #22) > After landing all dependencies, this applies cleanly. Thank you guys! > > v1-train: 25c80bc0acb1b6b541b3c5c07d8e2301f0d85c8d ^^^^ Wrong commit number ^^^^ v1-train: 186d31782d8cadb296661a7d104bc28846d1dfb9
Updated•11 years ago
|
Flags: in-moztrap?
Updated•11 years ago
|
Flags: in-moztrap? → in-moztrap+
You need to log in
before you can comment on or make changes to this bug.
Description
•