I know there was an earlier fix related to "background-image: url(/sites/all/themes/mayo/images/pat-0.png)" showing up when the settings were blank. It was supposed to have been fixed in the Feb dev version, but I currently am setting everything to blank, white, no watermark and no background image. In Chrome I get a white header as expected, but in IE8 I am getting a colored background dithered from blue to black. I firebugged it and found the 'pat-0.png' in there, which doesn't exist - but that STILL doesn't explain where the dithered background is coming from?

How can I clear out all background colors, images, watermarks, etc? I'm going to attempt to upload a pure white background image, I hope it doesn't scoot everything around though.

I suppose this is a bug...

Comments

Smenzo’s picture

Smenzo commented

Confirmed - I have the same issue.
I believe its caused by the mayo/css/colors.css which has a Internet Explorer filter 'hack' applying a gradient - which does not get removed when you change the theme settings. Firefox and other browsers ignore the filter attribute so you don't see the issue.

#header {
  background-color: #019bf9;
  background-image: -webkit-gradient(linear, left top, right top, from(#019bf9), to(#a3dcff));
  background-image: -moz-linear-gradient(0deg, #019bf9, #a3dcff);
  border-color: #fbfbfb;
  /* for IE 5.5-7 */
  filter:progid:DXImageTransform.Microsoft.Gradient(StartColorStr=#019bf9, EndColorStr=#a3dcff, GradientType=1);
  /* for IE 8 */
  -ms-filter:"progid:DXImageTransform.Microsoft.gradient(startColorstr=#019bf9, endColorstr=#a3dcff, GradientType=1)";
}

One solution is to remove these IE filter hacks (and the Firefox/Safari -webkit -moz prefixes which are no longer needed).

Unless the theme developers have a smart way to remove the filters when theme settings are changed?

Smenzo’s picture

Smenzo commented

Discovered cause - using the 'custom' color scheme, some of the colors were set to '#fffff' instead of '#ffffff' (one of the f's was missing).

So not sure if this is an issue with the colors module initialising the values when 'custom' color scheme was selected, an issue with the Mayo implementation of the colors module, or a mistake by the site administrator missing one of the f's when they entered the value.

However if I update the header left, header right and node backgrounds to #ffffff and save, then clear caches, the problem appears to be fixed.

Smenzo’s picture

Smenzo commented

Update - if I manually try to enter '#fffff' then it gets validated as an invalid hexadecimal CSS color value so that rules out mistake by the site administrator missing one of the f's when they entered the value.

Must be a bug in colors module or a bug in the Mayo implementation of the colors module?

mermentau’s picture

mermentau commented
Status: Active » Closed (cannot reproduce)

The problem with the incorrect #fffff as opposed to #ffffff seems to be not reproducible at this time. If there is more information feel free to re-open. The 404's caused by the missing images/pat-0.png should be corrected now in the dev version.

Todd Young’s picture

Todd Young commented

This also happens when you use three-digit color codes like #FFF. The fix is very simple - don't do dat!