Closed Bug 816978 Opened 12 years ago Closed 12 years ago

l10n.js fails when try to load a non-existant resource

Categories

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

Product:
Firefox OS Graveyard
Component:
Gaia
Platform:
x86
macOS
Type:
defect

Tracking

(blocking-basecamp:+)

Status:
RESOLVED DUPLICATE of bug 817286
Milestone:
B2G C3 (12dec-1jan)
Project Flags:
blocking-basecamp +

People

(Reporter: willyaranda, Assigned: kaze)

Details

(Keywords: l12y, Whiteboard: [target:12/21])

Keywords: l12y
This also break the FTU the first time it's loaded (clean flash with our internal builds):

E/GeckoConsole(  109): [JavaScript Error: "NS_ERROR_FAILURE: Failure" {file: "app://communications.gaiamobile.org/shared/js/l10n.js" line: 218}]

The library works perfectly if you launch the FTU from the developer menu once you configure your phone.
This is really bad and should be quick to fix. Nominating for blocking-basecamp.
blocking-basecamp: --- → ?
blocking-basecamp: ? → +
Priority: -- → P1
this should use

xhr.onerror and xhr.ontimeout

I'll do the pull request if so.
Mass Modify: All un-milestoned, unresolved blocking-basecamp+ bugs are being moved into the C3 milestone. Note that the target milestone does not mean that these bugs can't be resolved prior to 12/10, rather C2 bugs should be prioritized ahead of C3 bugs.
Target Milestone: --- → B2G C3 (12dec-1jan)
Any progress? This is blocking the FTU experience, among other apps to be localized properly (like Settings)
I have a quick and dirty patch, looking for a better one atm…
Whiteboard: [target:12/21]
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.