Open
Bug 186473
Opened 23 years ago
Updated 3 years ago
The background color specified in the user style sheet should not affect the color of the buttons or the scroll bar.
Categories
(Core :: CSS Parsing and Computation, defect, P4)
Core
CSS Parsing and Computation
Tracking
()
NEW
People
(Reporter: kaleida, Unassigned)
References
()
Details
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)
Build Identifier: Mozilla 1.2.1
If the user specifies in the userContent.css file that his colors should be
used, the buttons on Web pages, the scroll bar arrows, and the the scoll bar
slider all have the specified background color.
Reproducible: Always
Steps to Reproduce:
1. Create a user style sheet userContent.css in the C:\Documents and
Settings\user_id\Application Data\Mozilla\Profiles\Default User\chrome folder.
2. Make sure that the style sheet contains:
* { color: black !important;
background: white !important;
}
3. Open the Google.com home page. Note that the buttons are white.
4. Search for anything. Note that the scroll bar arrows and slider are white.
Actual Results:
The colors specified in the user syle sheet should not affect the color of the
buttons on the Web pages nor the colors of the scroll bar arrows and slide bar.
Expected Results:
The buttons and the scroll bar should be displayed in gray.
Comment 2•23 years ago
|
||
->Style
Assignee: asa → dbaron
Component: Browser-General → Style System
QA Contact: asa → ian
Really a duplicate of bug 21890, except that's marked fixed. Confirming.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Scrollbars are handled out of userContent.css, not userChrome.css.
http://flii.us/myworks/phoenix/pages/content.html
If anyone can explain to me why, I'd like to know. Does this go along the lines
of allowing a webpage to color the scrollbar like in IE? Except that we don't
actually allow that.
Assignee: dbaron → nobody
QA Contact: ian → style-system
OS: Windows 2000 → All
Priority: -- → P4
Hardware: x86 → All
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•