For android and b2g, we don't want to localize toolkit no more, but just overload a few select toolkit files in a new provider. Thus a trick like getSelectedLocale("global") to get the best match we have for a given locale setting won't work no more. I propose we factor that into the chrome registry, and just iterate over providers and see how good a match we can find in all registered packages.
I don't see how I can make this work for the RTL code on the caller side, so I'll WONTFIX this in favor of a solution where we can make the chrome registry look at an alternative package instead.
No longer blocks: 792077
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.