Closed Bug 1796626 Opened 3 years ago Closed 3 years ago

Firefox 107 ignore wider sidebar width via uerChrome.css

Categories

(Toolkit :: Application Update, defect)

Firefox 107
defect

Tracking

()

RESOLVED INVALID

People

(Reporter: info2, Unassigned)

Details

Attachments

(1 file)

Attached file userChrome.css

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:107.0) Gecko/20100101 Firefox/107.0

Steps to reproduce:

I created a userChrome.css with
#sidebar {
max-width: none !important;
min-width: 0px !important; }

This is needed for a wider sidebar and this worked fine until the beta update channel installed Firefox 107b2

Actual results:

The Sidebar is so small like without the userChrome.css, to small for me.

Expected results:

#sidebar {
max-width: none !important;
min-width: 0px !important; }
should work again.
There is no possibility anymore to leave the beta channel without disabling updates and waiting until the final version is out. Otherwise firefox refiusing to take over my profile. This is also not good for me.

The Bugbug bot thinks this bug should belong to the 'Toolkit::Application Update' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Application Update
Product: Firefox → Toolkit

We kind of explicitly do not provide support for userChrome.css. To quote Firefox advanced customization and configuration options:

Mozilla highly recommends that only the developers consider these customizations, as they could cause unexpected behavior or even break Firefox.

Firefox is a work in progress and, to allow for continuous innovation, Mozilla cannot guarantee that future updates won’t impact these customizations. For this reason, Mozilla does not officially support setting custom style rules with a userChrome.css file or using the about:config configuration editor to change preference settings.

Which is to say, neither the selectors nor the CSS that we use to style Firefox constitute a stable API, and we are going to make changes to them from time to time, likely without making any sort of announcement or changing any documentation. If you use userChrome.css to style these things, they will likely need to be maintained over time to keep up with our changes to the code.


Purely unofficially, I suspect that this patch is probably what broke your userChrome.css, and likely you need to override the max-width on #sidebar-box in order to make this work. But I'm not making any promises that that is the right solution or the whole solution.

Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: