This bug is for phase 1
"We've identified a need in several markets (particularly where English is not generally understood) for the ability to filter AMO for specific locales. For instance, in JA, there should be a checkbox (checked by default but remembered on a per browser basis) that filters all search, collection, and listing content by whether or not they contain JA specific translations. " We're doing this in search now. We back fill other locales. The browse view... this could get very gross... we could do backfilling here, or something else... but this might need to be chowsed it's got a lot of checkboxes and will just get fugly.
Created attachment 414095 [details] [diff] [review] v1 Adds a checkbox to the browse view. Stephen/Krupa, This should be in Litmus for sure, but I can't figure out a useful automated test (until we move it over to Django), my automation idea is just verifying that we're looking at ja translations if we went to a /ja/ brows page: /ja/firefox/browse/type:1/cat:all?show=20&locale-only=on&sort=newest That we verify that all the translations we're seeing are ja-only.
Dave: there's a flag for that (tm); marked :-)
Comment on attachment 414095 [details] [diff] [review] v1 I'm fine with the code, but the UI wording is confusing (I wish I would have noticed the wording of the "show Firefox-only add-ons" too). I think that makes it more difficult for L10n, why not just: Show only $lang add-ons Also, you can add the complete locale name to an abbr or alt tag. Use localeDetails::getNativeNameForLocale()
Created attachment 414120 [details] [diff] [review] v2 Didn't feel like converting localeDetails to static, but this works.
Comment on attachment 414120 [details] [diff] [review] v2 That works too
r56724 | firstname.lastname@example.org | 2009-11-23 15:25:20 -0800 (Mon, 23 Nov 2009) | 2 li [bug 528391] Addeda checkbox
8 years ago