Open GoogleCodeExporter opened 9 years ago
Don't have time to look at this carefully, but version 2.7 introduced some
locale changes which might possibly have resolved this problem. It also allowed
extensions to add a "langReady" callback which is passed an object with "lang"
and "uiStrings" properties whenever the locale data is first made available or
changed by the user and this callback will not be invoked until the locale data
is available. Extensions can add strings to all locales and utilize this
mechanism. If you have time, you might check whether the version in trunk still
has this issue.
Original comment by bret...@gmail.com
on 22 May 2014 at 11:36
Original issue reported on code.google.com by
chrille....@gmail.com
on 31 Mar 2011 at 9:34