Open Bug 1900086 Opened 4 months ago Updated 4 months ago

Show a warning that userChrome.css is active after major version browser updates

Categories

(Firefox :: Toolbars and Customization, enhancement)

Product:
Firefox
Component:
Toolbars and Customization
Platform:
Desktop
All
Type:
enhancement

Tracking

()

People

(Reporter: 08xjcec48, Unassigned)

Details

Steps to reproduce:

This is a very common issue:

  • Enable toolkit.legacyUserProfileCustomizations.stylesheets
  • Paste some code copied from the Internet into userChrome.css
  • Forget about it

Actual results:

After a few browser updates, those CSS hacks need updates. Firefox looks "broken" to users, and they create posts about it on support communities.

Expected results:

Firefox could show a warning bar after every browser update telling users that they have set up a userChrome.css file, and that it needs to be edited or disabled in case the GUI looks funny.

Component: Untriaged → Toolbars and Customization
OS: Unspecified → All
Hardware: Unspecified → Desktop

I have a few questions:

  1. How frequently do these updates actually produce a problem? Signal/noise ratio would be pretty bad if it's 1-in-10. Then people get habituated to clicking the warning message (and/or annoyed about it and they complain in the support forum about that!). Then when things break it may or may not work in reminding them it may be related...
  2. What kind of breakage are we talking about (i.e. do you have some links to example support threads where this happens) ?
  3. Aren't the people who use userChrome.css just going to then write userChrome.css to remove the annoying warning (see #1), which would defeat the point of all this work?
Severity: -- → N/A
Status: UNCONFIRMED → NEW
Type: defect → enhancement
Ever confirmed: true
Flags: needinfo?(08xjcec48)
Summary: Show a warning that userChrome.css is active after browser updates → Show a warning that userChrome.css is active after major version browser updates
You need to log in before you can comment on or make changes to this bug.