34389 - [feature] Need user.css and scrollbars.css loaded as backstop style sheets

Status: VERIFIED FIXED

(Core :: XUL, defect, P1)

Description

[Akkana Peck]

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.

Comment 1

[Peter Trudelle]

Mass-moving all M16 non-feature bugs to M17, which we still consider to be 
part of beta2

Comment 2

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

See also bug 6782.

Comment 3

[David Hyatt]

This is a skins bug.

Comment 4

[Peter Trudelle]

reassigning to saari to load-balance

Comment 5

[David Hyatt]

Fixed!

Comment 6

[David Hyatt]

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.

Comment 7

[John Morrison]

verified fixed