CSS color naming
- Started
- Last post
- 14 Responses
- mijlee
Am having a huge headache here. I am getting errors when validating stylesheets with my color naming. Here is the error I am getting;
Parse Error - #E0F0FF
- blaw0
that's not a valid hex.
- MX_OnD0
why is it not valid??
- infostruct0
It's valid, it is a light blue, right? Not a web color, but css shouldn't care.
- ETM0
I don't think it should matter, but then again, have you tried in all lower case... ? Give it a shot and validate again.
- 4est0
If it doesnt validate the W3C will come and eat you,. Better fix it!
- Dancer0
This maybe a stupid suggestion but is the "#" actually in your style sheet?
- blaw0
It's valid, it is a light blue, right? Not a web color, but css shouldn't care.
infostruct
(Jun 28 05, 07:51)
---
that's right, i'm wrong. sorry about that.
- 4est0
I cracked a joke earlier...but you should really read this article by Mike Davidson creator of the sIfr flash header so many people around here use and love.
- Hello-Sexy0
post your css...
- mijlee0
There was some eronious charecter in my code.
Coudn't see it on the mac but when viewd on a PC there was an unknown character (shown as a square) between the hex and the semi colon.
- mr7400
I think Dancer might be right.
I've run into problems using the # approach. Just leave that out and try it again.
- mr7400
E0F0FF
- foreign0
yeah, when you validate your css at w3c, it checks your xhtml document first, and returns as "not validated" if there's a problem with the code in your xhtml.
for some reason the check is more strict than when simply validating your xhtml.
- foreign0
ok, i read the thread wrong.