Open Bug 1507151 Opened 6 years ago Updated 2 years ago

The slow connectivity error from the Language Settings modal is displayed after incorrect timing

Categories

(Firefox :: Settings UI, defect, P2)

defect

Tracking

()

Tracking Status
firefox63 --- unaffected
firefox64 --- unaffected
firefox65 --- affected

People

(Reporter: danibodea, Unassigned)

References

(Blocks 1 open bug)

Details

[Note]:
- when the user limits his connectivity severely and attempts to download language packs from the browser's preferences, he will notice that the network connectivity error is displayed after incorrect timing.

[Affected versions]:
- v64.0a1

[Affected platforms]:
- most probably all; only tested on windows due to internet speed limiter application compatibility.

[Preconditions]:
1. Download and install the NetBalancer application from:
https://netbalancer.com/download 
(Windows restart required)
2. Open browser and set the following preferences from about:config
intl.multilingual.enabled - set to "TRUE"
intl.multilingual.downloadEnabled - set to "TRUE"
extensions.getAddons.langpacks.url - set to "https://mock-amo-language-tools.glitch.me/"
extensions.langpacks.signatures.required - set to "FALSE"
(Browser restart required)
3. Open NetBalancer and limit the upload and download limit of every firefox process to 1KB/s.

[Steps to reproduce]:
1. Open "Preferences" and go to "Language Preferences" section;
2. Click on "Set Alternatives..." button;
3. Click on the "Select a language to add..." drop-down;
4. Click on the "Search for more languages..." option;

[Expected result]:
- A loading animation is displayed on the drop-down, displaying "Searching for languages..." AND an error message is displayed after 90 seconds.

[Actual result]:
- A loading animation is displayed on the drop-down, displaying "Searching for languages..." AND an error message is displayed after 30-40 seconds.

[Additional notes]:
- If the user then, closes the modal, reopens it and retries to search for new language packs, the loading animation will be displayed for about 120-310 seconds before showing the network error.
Mark, can you set a priority here?
Flags: needinfo?(mstriemer)
Flags: needinfo?(mstriemer)
Priority: -- → P2
The time until an error is displayed in case of Ubuntu 18 is 120+ seconds in the first try.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.