Re: Validator: #autoXML196424196424 - what? :-)

Hi Thomas,

> run this validator check:
> http://jigsaw.w3.org/css-validator/validator?uri=http%3A%2F%2Fwww.kiss-chance.de&warning=1&profile=css21&usermedium=all

> Towards the bottom I get a warning about a Tag named
> "#autoXML196424196424" for http://www.kiss-chance.de (the page, not the
> style sheet, which is /css/style_creme.css and analyzed above) in line 111.
>
> Line 111 does not have any style information. The warning is about
> font-families (can't copy/paste here, because I get the german validator
> output). There is not a single font family style in that HTML code.

The warning concerns code in line 112 of your HTML source, where you
have a style attribute with the following value:

  style="color: #7b2317; font-family: courier new, courier; font-weight:bolder;"

The font family "courier new", should be quoted.

> In line 112 the validator complains about the same foreground and
> background color for the contexts "body" and "#autoXML196424196425"
> (Note: This is a different name than the one mentioned above!).
>
> What does this mean?

Actually you have quite a few warnings about background and text
colours. The reason for these warnings is, that user Style sheets may
render your page unreadable, if not both background and text colours
are set.

In your Style sheet you specify a white background and in line 113 of
your HTML source you have:

  <font style='color: #fff;'>

If you do not set any background colour for this FONT element, it is
by default transparent. Now, as the only parent with a background is a
table with background image, once images are disabled, the background
for the whole table, including the FONT element, becomes white.
Consequently, your text is white on white, unreadable.

> Other errors I get and not fully understand are about "expression", a
> workaround I use to accomplish some positioning in IE6.
>
> About expression("62px") the validator says that this would not be a
> height value. Does the validator have a problem with string expressions,
> or is this really outside the specifications (even though it works).
> [...]
> The question is, does the validator have a problem with this, are the
> errors misleading, or is this IE only stuff that really shouldn't work.

This is an IE-only proprietary property. The validator is right in
pointing out these errors.


Cheers,

jens
-- 
Jens Brueckmann
http://www.yalf.de

Received on Tuesday, 25 September 2007 10:38:12 UTC