[Tracking Requested - why for this release]: unusual visual change

Turn on Dark mode

Actual results:
bright background of toolbar and true black background of address bar/search bar drop down in dark mode
see attached

Expected Results:
Shuold not change from 109

:dao, since you are the author of the regressor, bug 1704347, could you take a look? Also, could you set the severity field?

For more information, please visit auto_nag documentation.

The issue with the background of the Addressbar also affects Light Mode, at least for the Toolbar color (please see my duplicate Bug 1806966.) I am adding the screenshot here too. Thanks.

My two cents: As with other changes in Firefox and other desktop OSes resulting in low contrast widgets, there are many people out there with subpar displays that will see these changes very differently from those of us with higher end gear - just because it may look great on a mockup, it doesn't mean that it will look great on an end users's device - we have no control over the quality of the display the person is viewing this on.

FWIW, I think the change to the tabstrip is fine - it is the toolbar (and inputs within) that is going to get the brunt of the negative feedback here. While the tabstrip change actually fixes bug 1704347, the toolbar change now makes it "less easy to distinguish inputs in toolbar" -- that may be by design, but that makes the application less usable.

The bug is marked as tracked for firefox110 (nightly). However, the bug still isn't assigned.

:cbellini, could you please find an assignee for this tracked bug? Given that it is a regression and we know the cause, we could also simply backout the regressor. If you disagree with the tracking decision, please talk with the release managers.

For more information, please visit auto_nag documentation.

@Misha -- Wanted to get you visibility on this one. Thoughts?

This is a reminder regarding comment #6!

The bug is marked as tracked for firefox110 (nightly). We have limited time to fix this, the soft freeze is in 14 days. However, the bug still isn't assigned.

This is a reminder regarding comment #6!

The bug is marked as tracked for firefox110 (nightly). We have limited time to fix this, the soft freeze is in 13 days. However, the bug still isn't assigned.

This is a reminder regarding comment #6!

The bug is marked as tracked for firefox110 (nightly). We have limited time to fix this, the soft freeze is in 10 days. However, the bug still isn't assigned.

This is a reminder regarding comment #6!

The bug is marked as tracked for firefox110 (nightly). We have limited time to fix this, the soft freeze is in 9 days. However, the bug still isn't assigned.

This is a reminder regarding comment #6!

The bug is marked as tracked for firefox110 (nightly). We have limited time to fix this, the soft freeze is in 8 days. However, the bug still isn't assigned.

Fixed by backout in 110

Reproduced this issue on an affected Nightly build from 2022-12-21, on Windows 10 x64.
Verified as fixed on Firefox 110.0b2 (20230117185909) on Windows 10, macOS 10.15 and Ubuntu 21.04 on both Light and Dark themes.