Closed Bug 1771459 Opened 2 years ago Closed 2 years ago

Upper UI becomes invisible when about:preferences tab is the active tab

Categories

(Core :: Widget: Cocoa, defect)

Firefox 102
Unspecified
macOS
defect

Tracking

()

VERIFIED FIXED
103 Branch
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)

Affected version

  • Nightly 102.0a1

Affected platforms

  • MacOS 11.6
  • MacOS 12.0.1
  • MacOS 11 - Apple M1

Steps to reproduce

  1. Launch Firefox.
  2. 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

Has Regression Range: --- → yes
Has STR: --- → yes

: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.

Flags: needinfo?(peter.magyari)
Component: Tabbed Browser → Widget: Cocoa
Flags: needinfo?(peter.magyari)
Product: Firefox → Core
Regressed by: 1731136

:bradwerth, since you are the author of the regressor, bug 1731136, could you take a look?
For more information, please visit auto_nag documentation.

Flags: needinfo?(bwerth)

[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.

That was fixed by the backout of bug 1731136

Flags: needinfo?(bwerth)

Verified on Firefox Nightly 102.0a1 (20220529190847)

[Tracking Requested - why for this release]: same reason as comment 3.

Is this again a problem after the relanding of bug 1731136?

(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.

Flags: needinfo?(peter.magyari)

FWIW I can't repro on nightly either.
Tracking to ensure we get confirmation from the reporter and update the 103 status appropriately

The issue does not occur on Nightly 103.0a1.

Flags: needinfo?(peter.magyari)
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
Target Milestone: --- → 103 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: