In Tools->Options->General->Languages, if you select a language to add, and click the "Add" button, the language appears at the bottom of the list of active languages. It should appear on top of the list instead. Bug 181541 comment 110 said: > I expect that new users want to "Add" a language because they want their > favorite web site to show up in their language if it's available. > So I would like that adding a language adds on top of the list, first position, > instead of last position. The basic configuration steps would be to add my > native language, then bump OK, that's all, don't need to "Move up".
*** Bug 252194 has been marked as a duplicate of this bug. ***
I'm assuming by the fact that Steffen filed this twice that he intends to do this himself. :) Steffen, sooner is better on this :)
sorry for bugspam, long-overdue mass reassign of ancient QA contact bugs, filter on "beltznerLovesGoats" to get rid of this mass change
Created attachment 574082 [details] [diff] [review] Add the new language at the top of the list Adds the new language at the top of the array (at the function), concatenates the old string and then makes it the new preference value. Requesting review to :vlad as the file being modified by the patch hasn't been reviewed by anybody (as per the log info). During my testing, I've noticed that, when opening the Languages dialog box, the list of available languages includes those that have been accepted by user, also. When adding a new one, this list is updated. Don't know if this is a desired behaviour (I doubt it). This is also how it works on Firefox 8 Windows (last release at the date this is written).
Thanks for taking this, I forgot about his bug years ago... (In reply to Javi Rueda from comment #4) > Requesting review to :vlad as the file being modified by the patch hasn't > been reviewed by anybody (as per the log info). I reintroduced the dialog in bug 181541 (r=mconnor). The code got refactored with the introduction of <preference> element by Ben Goodger (bug 274712, no review; he also introduced the trailing whitespace and the typo...). Further changes are in the CVS log: http://bonsai.mozilla.org/cvslog.cgi?file=mozilla/browser/components/preferences/languages.js&rev=HEAD&mark=1.10
Is Mano a better reviewer of this code? Also, if you are intereted again in this bug, you can take it again, no problem to me :-)
It probably doesn't make a big difference - as long as you don't pick Gavin :) And this bug is definitely yours.
(In reply to Steffen Wilberg from comment #7) > It probably doesn't make a big difference - as long as you don't pick Gavin Please stop spreading the rumour that I'm not responsive to review requests, since it isn't true :)
Comment on attachment 574082 [details] [diff] [review] Add the new language at the top of the list Just use: if (preference.value == "") preference.value = selectedID; else preference.value = arrayOfPrefs.unshift(selectedID).join(",");
(In reply to Gavin Sharp (use firstname.lastname@example.org for email) from comment #8) > Please stop spreading the rumour that I'm not responsive to review requests, > since it isn't true :) Guess I should do a better job at nagging about 8-week-old review requests then :)
Created attachment 577457 [details] [diff] [review] patch 1.1 Using code from comment 9. unshift() returns an integer, not the array object, so code had to be split up into unshifting and joining.
Comment on attachment 577457 [details] [diff] [review] patch 1.1 >diff --git a/browser/components/preferences/languages.js b/browser/components/preferences/languages.js > var arrayOfPrefs = preference.value.toLowerCase().split(/\s*,\s*/); Using arrayOfPrefs to set the value will lower-case the pref, is that a problem? Looks like it isn't, but would be good to confirm.
http://mxr.mozilla.org/mozilla-central/source/browser/components/preferences/languages.js#66 resource://gre/res/language.properties is the full list, including languages we don't show in the UI, and it's all lower-case, language and region. According to http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.10, all tags are case- insensitive.