The way garland stores the style.css when you edit the colors is rather inconvenient. I've been trying to debug layout problems and have been immensely frustrated that the changes I've been making to style.css weren't reflected in the browser.

Well, I finally discovered that when you set a custom color (as I have) the style.css is modified and copied to .../files/color/garland-code/style.css

Hurmph!

I would think a solution would be to define colors.css to store the colors of the elements, and do the trick of copying that to .../files when the colors are modified. You would store the rest of the items (layout etc) in style.css.

Comments

tstoeckler’s picture

tstoeckler
he/him
Primary language German
Location Essen, Germany
commented
Version: 5.0-beta2 » 8.x-dev

Still applies.
Bartik introduced the notion of a "colors.css" with all color-module-overridable declarations in it. I don't know any precedent for using a plural word for a file name (ie I think it should be "color.css"), but either way, Garland should follow suit. If #911054: Remove Garland from Core gets in (oh dear...), then this is of course obsolete.

amateescu’s picture

amateescu commented
Status: Active » Closed (won't fix)

#911054: Remove Garland from Core is in, so marking this as obsolete :)