[macOS] Text in the crash reporter dialog is not localized for the non-US FF builds
Categories
(Toolkit :: Crash Reporting, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr115 | --- | unaffected |
firefox125 | --- | unaffected |
firefox126 | + | verified |
firefox127 | + | verified |
firefox128 | --- | verified |
People
(Reporter: cgeorgiu, Assigned: afranchuk)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
48 bytes,
text/x-phabricator-request
|
dmeehan
:
approval-mozilla-beta+
dmeehan
:
approval-mozilla-release+
|
Details | Review |
Found in
- 126.0 RC2
Affected versions
- 127.0a1 Nightly
- 126.0 RC2
Tested platforms
- Affected platforms: macOS 12, macOS 13
- Unaffected platforms: Windows, Ubuntu
Preconditions
- Have a localized build downloaded, e.g. "it", "fr" or "de".
- The build is installed on the test machine.
Steps to reproduce
- Launch Firefox.
- Go to "about:crashparent" in a new tab.
- Pay attention to the text inside the crash reporter dialog
Expected result
- The text inside the crash reporter dialog is accordinagly translated to the tested build ("it", "fr" or "de").
Actual result
- The text inside the crash reporter dialog is not translated to the tested build ("it", "fr" or "de").
Regression range
- It seems that the issue is not repro with Firefox 125.0.3. I will investigate further asap in order to find a regression range.
Reporter | ||
Updated•4 months ago
|
Updated•4 months ago
|
Updated•4 months ago
|
Assignee | ||
Comment 1•4 months ago
|
||
The crash reporter binary is in a different location in macOS installations, so it cannot locate the omnijar.
Updated•4 months ago
|
Assignee | ||
Comment 2•4 months ago
|
||
I have a fix for this. It is cumbersome to verify since it changed a portion of shared code and I want to verify that other platforms are not affected. I'm verifying now.
Assignee | ||
Comment 3•4 months ago
|
||
The branding was also potentially not read correctly (from the browser
omnijar) as a result of incorrect merging of changes from another
commit, however the impact of this is far less as the branding is likely
similar across locales.
Updated•4 months ago
|
Reporter | ||
Comment 4•4 months ago
|
||
(In reply to Ciprian Georgiu, Desktop QA from comment #0)
Regression range
- It seems that the issue is not repro with Firefox 125.0.3. I will investigate further asap in order to find a regression range.
I can reproduce the bug after the landing of https://bugzilla.mozilla.org/show_bug.cgi?id=1759175 in Nightly 125.0a1 (2024-03-08). With a pre-patch Nigthly build (2024-03-06), I cannot reproduce the issue. Unfortunately, I cannot pinpoint for sure the exact bug since I had to manually do the regression range.
Although this is already assigned, I hope this info helps.
Pushed by gsvelto@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/080acbd234b3 Fix location of the omnijar file(s) on macos r=gsvelto
Comment 6•4 months ago
|
||
bugherder |
Comment 7•4 months ago
|
||
Comment on attachment 9401120 [details]
Bug 1896097 - Fix location of the omnijar file(s) on macos r=gsvelto
Beta/Release Uplift Approval Request
- User impact if declined: The crash reporting dialog is not localized
- Is this code covered by automated tests?: No
- Has the fix been verified in Nightly?: Yes
- Needs manual test from QE?: Yes
- If yes, steps to reproduce: 1. Download a localized build
- Run Firefox and crash it by navigating to about:crashparent
- Check if the crash reporting client opens and is localized in the same language as Firefox
- List of other uplifts needed: None
- Risk to taking this patch: Medium
- Why is the change risky/not risky? (and alternatives if risky): We tested the patch thoroughly during development, but this code affects Windows, macOS and Linux differently. There's a fair bit of complexity involved.
- String changes made/needed: none
- Is Android affected?: No
Updated•4 months ago
|
Comment 8•4 months ago
|
||
Set release status flags based on info from the regressing bug 1759175
Comment 9•4 months ago
|
||
Comment on attachment 9401120 [details]
Bug 1896097 - Fix location of the omnijar file(s) on macos r=gsvelto
Approved for 127.0b2
Comment 10•4 months ago
|
||
uplift |
https://hg.mozilla.org/releases/mozilla-beta/rev/621635c80af8
Updated•4 months ago
|
Updated•4 months ago
|
Reporter | ||
Comment 11•4 months ago
|
||
I've confirmed that this issue is fixed in the latest Nightly 128.0a1 ("zh-TW", "it", "de") on macOS 13. I'll verify on Beta 127 as well once the localization builds are available.
Donal, I assume you intended to change the flag to fixed in FF 127, not 126.
Comment 12•4 months ago
|
||
Donal, I assume you intended to change the flag to fixed in FF 127, not 126.
Yes, thanks. Corrected!
Reporter | ||
Comment 13•4 months ago
|
||
This is also verified as fixed on Beta 127.0b2 ("de", "fr" and "it" builds) on macOS 13.
Comment 14•4 months ago
|
||
Thank you for the testing & uplifts 🙏
Comment 15•4 months ago
|
||
Comment on attachment 9401120 [details]
Bug 1896097 - Fix location of the omnijar file(s) on macos r=gsvelto
Approved for 126.0.1
Comment 16•4 months ago
|
||
uplift |
https://hg.mozilla.org/releases/mozilla-release/rev/cd849606cd40
Updated•4 months ago
|
Updated•4 months ago
|
Reporter | ||
Comment 17•4 months ago
|
||
Verified as fixed on Firefox 126.0.1 with "de" and "fr" builds running macOS 13.
Description
•