Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.My scheme is defined as:
'schemes' => array(
'#1f6eb3,#2a5c8a,#b8d6f2,#999999,#1f6eb2' => t('generic (default)'),
),
My css that color module affects:
#sidebar-left .menu-name-primary-links a{color: #1f6eb3}
#sidebar-left .menu-name-primary-links a{color: #3f9cf2}
The result after another scheme or new custom scheme is applied:
#sidebar-left .menu-name-primary-links a{color: }
#sidebar-left .menu-name-primary-links a{color: #3e9bf2}
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | color-base-replaced-with-null-732938-3.patch | 554 bytes | bramvdkroef |
| #1 | color-base-replaced-with-null-732938-1.patch | 554 bytes | bramvdkroef |
Comments
Comment #1
bramvdkroef commentedThe bug is on line 387 of modules/color/color.module:
Every time the base color is found in the stylesheet it is replaced with the base color in the conversion palette; but since that color has been removed you get null (or "").
I don't know why such an obvious bug wasn't spotted before d6 was released, or why someone thought it was a good idea to put it in. It doesn't do anything other than screwing up stylesheets.
Comment #3
bramvdkroef commentedComment #4
fuzzy76 commentedDuplicate of #134321: if default color profile base and original style.css background color are the same, output is invalid CSS background:;