Upper UI becomes invisible when about:preferences tab is the active tab
Categories
(Core :: Widget: Cocoa, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr91 | --- | unaffected |
firefox100 | --- | unaffected |
firefox101 | --- | unaffected |
firefox102 | + | verified |
firefox103 | + | verified |
People
(Reporter: pmagyari, Unassigned)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
437.48 KB,
image/png
|
Details |
Affected version
- Nightly 102.0a1
Affected platforms
- MacOS 11.6
- MacOS 12.0.1
- MacOS 11 - Apple M1
Steps to reproduce
- Launch Firefox.
- Open settings (go to about:preferences).
Expected result
- The Tabs/URL bar/Navigation buttons are visible when about:preferences is the active tab
Actual result
- Tabs/URL bar/Navigation buttons are invisible when about:preferences is the active tab
Regression range
- Mozregression returned the following pushlog:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=fb0c469ac2fb9ed647bb174a047ea396f472adaf&tochange=f392452506ec9d23229240ca347a84bbf3ac1975
Reporter | ||
Updated•2 years ago
|
Comment 1•2 years ago
|
||
:peter.magyari, since this bug is a regression, could you fill (if possible) the regressed_by field?
For more information, please visit auto_nag documentation.
Reporter | ||
Updated•2 years ago
|
Comment 2•2 years ago
|
||
:bradwerth, since you are the author of the regressor, bug 1731136, could you take a look?
For more information, please visit auto_nag documentation.
Comment 3•2 years ago
•
|
||
[Tracking Requested - why for this release]:
It's not clear to me if bug 1731136 is riding with 102, but if so this is gonna be on beta next week, and the bug is bad enough that we should try and do something to prevent it shipping to release with 102.
Comment 4•2 years ago
|
||
That was fixed by the backout of bug 1731136
Updated•2 years ago
|
Reporter | ||
Comment 5•2 years ago
|
||
Verified on Firefox Nightly 102.0a1 (20220529190847)
Updated•2 years ago
|
Comment 6•2 years ago
|
||
[Tracking Requested - why for this release]: same reason as comment 3.
Is this again a problem after the relanding of bug 1731136?
Comment 7•2 years ago
|
||
(In reply to Marco Castelluccio [:marco] from comment #6)
[Tracking Requested - why for this release]: same reason as comment 3.
Is this again a problem after the relanding of bug 1731136?
I can't repro on current nightly, but let's check with the reporter.
Comment 8•2 years ago
|
||
FWIW I can't repro on nightly either.
Tracking to ensure we get confirmation from the reporter and update the 103 status appropriately
Reporter | ||
Comment 9•2 years ago
|
||
The issue does not occur on Nightly 103.0a1.
Updated•2 years ago
|
Updated•2 years ago
|
Description
•