Weird CSS values

invalid css color values that user claims to need

[NattheCat]

Has anyone ever seen or used the following as values for setting the color of borders or backgrounds in css code?

*INNERTABLEBGCOLOR*
*INNERTABLEBORDERCOLOR*
*INNERTABLEHEADBGCOLOR*

I have not been able to validate this, nor can I find anything on it on the web. It is in a file that I have since taken over, and the person who wrote it is not available for questions.

Anything would be appreciated.

[sonjay]

Those aren't part of the specs for either html or css. In what context are they used?

Are they used as a css class? e.g.:

.INNERTABLEBGCOLOR {
background-color: #eeeeee;
}

And I've seen scripts that set colors by assigning values to variables in a scripting language such as php, e.g.:

<?php
$INNERTABLEBGCOLOR = '#eeeeee';
?>
<table style="background-color: <?php echo $INNERTABLEBGCOLOR; ?>">

But all by themselves, in, say, a css style declaration or in straight html, they would have no effect, because they don't exist as standard tags.

[NattheCat]

Here is the code:
.class {
background-color: *INNERTABLEBGCOLOR*;
}

[g1smd]

I am guessing that the *dummy* value gets replaced with a real value when the code is run through a template engine or somesuch.

[Xapti]

Yeah, either some server-side scripting is replacing it, or it's just filler code meant to be replaced manually...

The answer to which it would be, is dependent on what the output looks like. The output must be going through the server so that the server side code can replace the value if that's what it's doing.
If the colors aren't default (or inherited), then that means something's replacing them. You can also look at the source code's output as well to verify if it's been given a value. If it's not assigned a color, then that means it's just placeholder text that's meant to be replaced with a value manually (why someone would do that though, I don't know)...do it yourself.