Bug 1777658 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Affected versions:
Beta: 103.0b3/20220630185738
Release: 102.0/20220623063721

Steps to reproduce:
1. Access https://addons.mozilla.org/en-US/firefox/language-tools/
2. Install a language pack, for example the German (Deutsch) language pack
3. Access about:preferences#general, scroll down to the “Language” section and from the drop down select “Deutsch”. The language pack will be applied as it can be seen from the interface changing from English to German
NOTE: Do not restart the browser
4. Go to Add-ons Manager and from either the “Recommended” or “Extensions” tabs, install one of the recommended add-ons.
5. Notice the initial add-on download doorhanger is still in English.
6. Click on the equivalent in German “Add” button to install the add-on
7. Notice the doorhanger that is displayed after the add-on has been installed contains a couple of words in English, along the lines of “Addon_Name was added”, while the rest of the strings are in German.
7. Remove the add-on installed at step 4.
8. Notice the add-on removal pop-up has the button strings in English.
9. Restart the browser
10. Go to Add-ons Manager and from either the “Recommended” or “Extensions” tabs, install one of the recommended add-ons.
11. Notice the download doorhanger is now in German and all subsequent displayed doorhangers are fully in German
12. Remove the add-on installed at step 10
13. Notice the add-on removal pop-up is fully in German

Actual:
Language packs are not fully/properly applied without restarting the browser.
Expected:
1. Language packs should be fully/properly applied without restarting the browser
OR
2. A notification should be displayed at the “Language” section of about:preferences#general, prompting the user to restart the browser in order to fully apply the language pack

NOTE:
Also notice that without a browser restart the descriptions on the add-on cards from Add-ons Manager are still in English, which might be a possible additional cause for the issue occurring.
Affected versions:
Beta: 103.0b3/20220630185738
Release: 102.0/20220623063721

Steps to reproduce:
1. Access https://addons.mozilla.org/en-US/firefox/language-tools/
2. Install a language pack, for example the German (Deutsch) language pack
3. Access about:preferences#general, scroll down to the “Language” section and from the drop down select “Deutsch”. The language pack will be applied as it can be seen from the interface changing from English to German
NOTE: Do not restart the browser
4. Go to Add-ons Manager and from either the “Recommended” or “Extensions” tabs, install one of the recommended add-ons.
5. Notice the initial add-on download doorhanger is still in English.
6. Click on the equivalent in German “Add” button to install the add-on
7. Notice the doorhanger that is displayed after the add-on has been installed contains a couple of words in English, along the lines of “Addon_Name was added”, while the rest of the strings are in German.
7. Remove the add-on installed at step 4.
8. Notice the add-on removal pop-up has the button strings in English.
9. Restart the browser
10. Go to Add-ons Manager and from either the “Recommended” or “Extensions” tabs, install one of the recommended add-ons.
11. Notice the download doorhanger is now in German and all subsequent displayed doorhangers are fully in German
12. Remove the add-on installed at step 10
13. Notice the add-on removal pop-up is fully in German

Actual:
Language packs are not fully/properly applied without restarting the browser.

Expected:
1. Language packs should be fully/properly applied without restarting the browser
OR
2. A notification should be displayed at the “Language” section of about:preferences#general, prompting the user to restart the browser in order to fully apply the language pack

NOTE:
Also notice that without a browser restart the descriptions on the add-on cards from Add-ons Manager are still in English, which might be a possible additional cause for the issue occurring.

Back to Bug 1777658 Comment 0