WordPress.com

1. emecu
   Member
   Mar 6, 2013, 8:36 PM

   Hi there,

   In CSS Customization some little yellow triangles with an "!" mark have been appearing warning trouble, I guess. One of them says, about a background-color line: "Fallback background-color (hex or RGB) should preced rgba background-color."

   Which my Hero theme obediently came with.... except that when a

   background-color: #000;

   precedes

   background-color: rgba(0,0,0,.5);

   the background is NOT transparent. When I take the first line off, it works perfectly (as it has always do before), but I get those annoying yellow warnings.

   How can I fix this?

   Thanks a lot in advance for your help.

   The blog I need help with is fdfot.wordpress.com.

2. designsimply
   Staff
   Mar 7, 2013, 3:22 AM

   Interesting report! From what I can tell so far, the CSS editor saves the duplicate property but it isn't output in the final CSS that is sent to the browser. I'm not sure why that's happening. I've reported the issue to our developers so it can be reviewed.

   The warning icons come from CSSLint if that interests you:
   https://github.com/stubbornella/csslint/wiki/Require-fallback-colors

   I think a couple of the warnings are quite strict personally (like the padding+width one), but overall, most (almost all) of them extremely helpful!

3. emecu
   Member
   Mar 7, 2013, 4:28 AM

   Thanks a lot, designsimply, for your interest. And for the link. Of course it interest me, it was driving me crazy!!! :-D I totally agree with your view of the warnings. I even love strictness when it leads you to some desirable result.... I see I have a long homework to do this weekend.

   Hopefully, the developers will generate a bright idea soon.

   Thanks again.

4. designsimply
   Staff
   Mar 7, 2013, 2:13 PM

   No problem! I consider that particular warning (the one about needing a fallback color) an okay warning :) but I do think it's a bug that adding the fallback makes the 2nd background-color property go away. So, basically, hang tight, use a single background-color property and ignore that particular warning for now (until the bug can be reviewed).

Topic Closed

This topic has been closed to new replies.