Closed
Bug 34389
Opened 25 years ago
Closed 25 years ago
[feature] Need user.css and scrollbars.css loaded as backstop style sheets
Categories
(Core :: XUL, defect, P1)
Tracking
()
VERIFIED
FIXED
M16
People
(Reporter: akkzilla, Assigned: saari)
References
Details
(Whiteboard: 1 day, 4/28)
Hyatt and I talked about this: we need a way for the user to have a default stylesheet, which could then be used to load things like XBL behavior as well as the more obvious CSS properties. This has to be merged in with what's read in from the other CSS sources, so that even though user.css is loaded last (since it isn't loaded until after the profile manager has run and chosen the appropriate profile), it still is able to override the previously set properties. Hyatt has talked to Pierre about this and thinks he knows a way to do this.
Updated•25 years ago
|
Status: NEW → ASSIGNED
Summary: Need user.css → Need user.css and scrollbars.css loaded as backstop style sheets
Target Milestone: --- → M16
Comment 1•25 years ago
|
||
Mass-moving all M16 non-feature bugs to M17, which we still consider to be part of beta2
Target Milestone: M16 → M17
Updated•25 years ago
|
Summary: Need user.css and scrollbars.css loaded as backstop style sheets → [feature] Need user.css and scrollbars.css loaded as backstop style sheets
Whiteboard: 1 day
Updated•25 years ago
|
Whiteboard: 1 day → 1 day, 4/28
Comment 4•25 years ago
|
||
reassigning to saari to load-balance
Assignee: hyatt → saari
Status: ASSIGNED → NEW
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Priority: P3 → P1
Comment 5•25 years ago
|
||
Fixed!
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Comment 6•25 years ago
|
||
The chrome registry is now capable of serving up an array of user stylesheets that sit between the user agent style sheet and any author style sheets. It occurs to me that this location might not always be optimal, i.e., you could make a case for a user stylesheet that actually overrides the author's style sheets. For now, I've hardcoded the array. The chrome registry serves up a stylesheet found in the profile dir under the chrome subdirectory, e.g., Users50/Default User/chrome/user.css. I've also hardcoded the positioning, namely in between ua.css and the author stylesheets. The chrome registry could quite easily begin persisting information about what user stylesheets to load. It could even quite easily offer up information about whether or not the stylesheets should override the author sheets or not. I'll accept patches on this if anyone gets motivated to work on it.
You need to log in
before you can comment on or make changes to this bug.
Description
•