Closed Bug 46839 Opened 24 years ago Closed 24 years ago

RFE: user style override switch

Categories

(Core :: CSS Parsing and Computation, enhancement, P3)

enhancement

Tracking

()

VERIFIED WONTFIX

People

(Reporter: fantasai.bugs, Assigned: pierre)

Details

Overview: Given the following cascade: 1.) ua.css (importing html.css) 2.) user prefs & user stylesheets 3.) author's presentational markup 4.) author stylesheet(s) 5.) author !important rules 6.) user stylesheet !important rules & user prefs override (always use my colors, etc.) I'm requesting a switch that will put level 2 between levels 5 & 6. <BLOCKQUOTE cite="news:3957E177.993BAC60@escape.com"> <!-- fantasai. "Re: user stylesheet". June 26, 2000. n.p.m.style --> This allows the user three options for controlling the document's style: 1.) Regular cascading rules (CSS2:6.4) 2.) User stylesheet (& preferences) override author's rules 3.) Author's stylesheets are disabled entirely. Especially as XML comes more into use, the option of disabling the author's stylehsheets entirely becomes less useful (you usually want to keep the author's 'display' rules intact). Thus the second option becomes more attractive--a restrictive user stylesheet on override can disable those CSS properties that are more likely to be abused (e.g. background, text color). </BLOCKQUOTE> This way, a user doesn't have to create duplicate stylesheets with !important rules, but can cause the "defaults" from the user prefs & stylesheets to override the author style rules (but not user !important rules) for a particularly annoying page via a switch, say, in the 'Use Style' submenu. (I'm quoting myself a lot recently. I wonder if that's a bad thing...)
The UI to enable the stylesheets or override them is, or will be, plenty configurable enough already. We don't need one more pref to control the cascade. Closed as WontFix.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WONTFIX
Verified WONTFIX
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.