Forum Moderators: open

Message Too Old, No Replies

weblint validation... cant seem to clear something up

(use "-x <extension>" to allow this) ?

         

deft_spyder

11:16 pm on Dec 20, 2002 (gmt 0)

10+ Year Member



When I run my site index.htm through the html validator at [ejk.cso.uiuc.edu...] I get this error.

line 9: attribute `TOPMARGIN' for <body> is extended markup (use "-x <extension>" to allow this).

I've cleared everything else up, but this markup problme remains for it, and everywhere CSS controls certain tags.

My question is, what exactly are they telling me to do? ( "-x <extension>")

wha huh?

korkus2000

11:23 pm on Dec 20, 2002 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



You should read this thread.
[webmasterworld.com...]

topmargin is not a valid attribute in html and will not validate.
You should use the w3c validator to see if it follows the w3c standard.
[validator.w3.org...]

Your validator chokes on XHTML tags like <img />

deft_spyder

11:33 pm on Dec 20, 2002 (gmt 0)

10+ Year Member



thanks...

do you happen to know what they are talking about when they say " -x <extension> "?

tedster

2:06 pm on Dec 21, 2002 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



I think that line about -x <extension> is about how to modify the VALIDATOR so it ignores certain non-standard code.

deft_spyder

5:05 pm on Dec 21, 2002 (gmt 0)

10+ Year Member



aha!

thankyou so much.... i was racking my brain trying to figure out what html that was... silly me.

g1smd

10:26 pm on Dec 21, 2002 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



TOPMARGIN and several other similar attributes are browser specific codes.

They are flagged as errors when using the validation checker. To exclude any particular attributes from being checked you use the -x command. By excluding them from the check, you remove the error message from the list. Using browser specific code means that your site will display differently in various browsers. However, all browsers just ignore code that they do not understand, so it is possible to have various work-arounds in place so that each browser sees code that produces the same results as each other.