Closed Bug 815919 Opened 13 years ago Closed 8 years ago

are we using nsURLFormatter in b2g?

Categories

(Firefox OS Graveyard :: General, defect)

defect
Not set
normal

Tracking

(blocking-basecamp:-)

RESOLVED WONTFIX
blocking-basecamp -

People

(Reporter: mozilla, Unassigned)

References

Details

(Whiteboard: [multilocale])

All things using nsURLFormatter could be an l10n issue
Whiteboard: [multilocale]
(In reply to Aki Sasaki [:aki] from comment #0) > All things using nsURLFormatter could be an l10n issue Pike/Aki - who can we confirm with about whether or not this will be an l10n issue? Will this be obvious once we have multi-locale builds in hand?
blocking-basecamp: --- → ?
I'm hoping this is obvious when we have multilocale builds. I don't know what the issue is, specifically, or how it would manifest; in this case I was just filing what was reported in email.
As long as our gecko multi-locale build makes it in, we're cool. Any changes I'd do to shrink the impact of locales to our install size would not break the chrome registry, and thus not break formatURL. I can quite safely say that because my first attempt did break it, and I've mentally blocked the options that would. I'm not sure how this should be marked up bug-wise to denote "plan in hand with multi-locale gecko matching up at least the locale coverage in gaia".
gecko multi-locale build are blocking, so we are cool. minus.
blocking-basecamp: ? → -
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.