Closed Bug 45850 Opened 24 years ago Closed 23 years ago

[CASCADE]user stylesheet is not overriding ua.css

Categories

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

defect

Tracking

()

RESOLVED DUPLICATE of bug 43220

People

(Reporter: fantasai.bugs, Assigned: pierre)

Details

(Keywords: css1, css2, testcase)

Attachments

(1 file)

Overview:

	According to both the CSS1 and CSS2 specifications, all rules in the
	user stylesheet completely override the UA styles, regardless of 
	specificity. This is not happening in Mozilla.

	CSS1:3.2 - http://www.w3.org/TR/REC-CSS1#cascading-order
	CSS2:6.4.1 - http://www.w3.org/TR/REC-CSS2/cascade.html#cascading-order

Steps to Reproduce, Actual Results, and Expected Results:

	Open up testcase (to be attached shortly) and follow directions therein.

Tested on Mozilla nightly build (id: 2000071810) on Windows 2000
Attached file UA vs. User - testcase
Keywords: css1, css2, testcase
QA Contact: chrisd → py8ieh=bugzilla
Summary: user stylesheet is not overriding ua.css → user stylesheet is not overriding ua.css [CASCADE]
Is this going to be looked at anytime soon?

I tried following the instructions for setting up user defined stylesheets
which, apparently, worked in M16.

http://www.oreillynet.com/pub/a/network/2000/06/30/magazine/mozilla_stylesheets.html

I tested it and it doesn't work in build MTrunk 200010260

Obviously this isn't going to prevent average browsing, but this really should
be working and could be of great concern for those with disabilities, since many
people may not be able to read a lot of web pages as they were intended to by
the developer.  A user might be colorblind and change the link presentation or
want all text to be 2em bigger than it is normally displayed or whatever.

Hopefully someone can get to this for the .9 release.

Jake
The instructions at the URL in the comment above are out of date.  The file
should now be called userContent.css, not user.css.
Keywords: access
Thanks, David!  I tried userContent.css and it worked great :-)

Not sure if the problem in this bug is still an issue.  I use !important for all my directives in the userContent.css stylesheet which overrides defaults no matter what.

Jake
Ian, this really isn't an accessibility bug. For that purpose, you have to put 
!important in order to override the author's styles, which is a non-issue here. 
Besides, most style rules in the user stylesheet will override ua.css through 
the specificity sort in any case.

Bug 43220 is an accessibility bug; denote that one as such instead.
Status: NEW → ASSIGNED
Summary: user stylesheet is not overriding ua.css [CASCADE] → [CASCADE]user stylesheet is not overriding ua.css
Point taken.
Keywords: access
Hey, I am still having problems. My style sheet is named userContent.css, and 
Mozilla is still using system colors for some forms. Like on Yahoo, my Style 
Sheet specifies blue for the submit button, and cyan for :hover. Well, I still 
have a system colored button but the :hover still works. This is a recent 
thing, my button used to be blue. And I don't have !important in my style 
sheet, nor should I have to use it. I don't want to use it because I just want 
my style sheet to style the forms that have no style already. Forms with style 
should still be allowed to display the author specifyed styles.
This last regression is probably coming from the recent changes to implement 
forms.css.  I'll have a look.
I opened bug 62304 for the problem described above.  A fix is attached.
It's going to be fixed with bug 43220.

*** This bug has been marked as a duplicate of 43220 ***
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: