Bug 1574501
Summary: | firefox doesn't pick up locale on the first run | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Jiri Prajzner <jprajzne> |
Component: | firefox | Assignee: | Martin Stransky <stransky> |
Status: | CLOSED WORKSFORME | QA Contact: | Desktop QE <desktop-qa-list> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.5 | CC: | tpelka |
Target Milestone: | rc | Keywords: | Regression |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-05-11 09:55:57 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1556893 |
Description
Jiri Prajzner
2018-05-03 12:37:26 UTC
Direct modification of "intl.locale.requested" fixes that - Firefox picks selected language for the first run. We may consider to remove the extension hacks here as WebExtension should not affect browser performance. (In reply to Martin Stransky from comment #2) > Direct modification of "intl.locale.requested" fixes that - Firefox picks > selected language for the first run. We may consider to remove the extension > hacks here as WebExtension should not affect browser performance. I was wrong here, intl.locale.requested solves nothing and we don't have a fix for that right now. Seems it it fixed with firefox-60.0-2.el7_5 (In reply to Tomas Pelka from comment #5) > Seems it it fixed with firefox-60.0-2.el7_5 I don't believe so, the bug is just less visible here. I already updated the errata about this bug. We use a distribution directory for extension which does not have this bug. Closing now as it affects internal builds only. So If I understand it correctly there are two workarounds but we don't wan't to implement and maintain any of them? I do admit this is definitely not a blocking issue and LANG should be take in account on second and following starts. But I bet there will be bug reports coming from customers confused by this race condition/regression. Please reconsider. (In reply to Tomas Pelka from comment #9) > So If I understand it correctly there are two workarounds but we don't wan't > to implement and maintain any of them? No, we will ship langpacks in distribution directory now so we won't have this issue any more. |