More string vs. localized pref failure.
http://mxr.mozilla.org/mozilla-central/source/mobile/android/chrome/content/browser.js#7634 is the code in question. Can we just use BrowserApp.getUALocalePref() here?
(In reply to Mike Connor [:mconnor] from comment #1) > http://mxr.mozilla.org/mozilla-central/source/mobile/android/chrome/content/ > browser.js#7634 is the code in question. Can we just use > BrowserApp.getUALocalePref() here? That sounds fine to me.
Created attachment 8562420 [details] [diff] [review] fennecDistroFix2
Attachment #8562420 - Flags: review?(rnewman)
Attachment #8562420 - Flags: review?(rnewman) → review+
Comment on attachment 8562420 [details] [diff] [review] fennecDistroFix2 Approval Request Comment [Feature/regressing bug #]: [User impact if declined]: [Describe test coverage new/current, TreeHerder]: [Risks and why]: low risk, only should impact localized distribution prefs. Since this is now completely broken, the pending distribution we're working on is clearly the first and only consumer. [String/UUID change made/needed]: none.
status-firefox36: --- → affected
status-firefox37: --- → affected
status-firefox38: --- → affected
Status: ASSIGNED → RESOLVED
Last Resolved: 3 years ago
status-firefox38: affected → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 38
status-firefox37: affected → fixed
status-firefox36: affected → fixed
You need to log in before you can comment on or make changes to this bug.