osdir.com
mailing list archive
Mozy Online Backup: 2GB Free. Automatic. Secure.

Subject: [VE][108] Error Message Feedback - msg#00146

List: org.w3c.validator

Date: Prev Next Index Thread: Prev Next Index
Hello,   I used your validation program to see how my site was, and I gave me a couple of incorrect errors.  For example, it said:  

Line 19, column 124: there is no attribute "MARGINHEIGHT"

...0000FF" vlink="#800080" marginheight="0" marginwidth="1" topmargin="0" leftma...

And you can see it in the line above.  Do I have to capitalize the marginheight or put quotes around it?  It also did this for
marginwidth, topmargin, leftmargin, hspace, vspace, and height.
I also was wondering what the "ALT" attribute was- it gave me MANY errors because I didn't have it.

Thanks,
Eric

Was this page helpful?
Yes No
Thread at a glance:

Previous Message by Date: click to view message preview

[VE][108] Error Message Feedback

So since when is height=”100%” not correct HTML 4.01 ?   Why does WC3 not supprt percentages as height for tables, etc.   1.      Line 15, column 60: there is no attribute "HEIGHT" <table border="0" cellspacing="2" cellpadding="0" height="100%"> You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead). This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information. How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute.   --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.718 / Virus Database: 474 - Release Date: 9-7-2004

Next Message by Date: click to view message preview

Re: validation of

You are absolutely right, of course. <noscript> is a block element. So why is it? Noscript should be able to replace <script> anywhere. I'm advertising a regular date on the first Friday of every month. Because it's a regular date, I can work out what the first Friday of next month is and use document.write to add the date to the document. I also want to link to a file that describes the date in greater detail. That's why the date is inside the link. However, not everybody has Javascript, so instead of saying, "Next show: 6th August" with the date written by a script, I want to add a noscript element so that non-scripting browsers say, "Next show: the first Friday of next month", which would also be a link to the detailed page. I don't understand why the specs should limit <noscript> to being a block element if <script> itself is allowed to be inline. I think that makes it harder to make accessible documents. Note that existing browsers have no trouble at all with <noscript> being inline (all the ones I've tested show my alternative text as I want them to when Javascript is turned off or unavailable and handle the link accordingly). I realise now that I made a mistake in understanding the spec, but now I see that, in this respect, the spec is daft anyway.

Previous Message by Thread: click to view message preview

Re: [VE][108] Error Message Feedback

On Jul 17, 2004, at 1:05, Geronimous wrote: So since when is height=”100%” not correct HTML 4.01 ? Always? http://www.w3.org/TR/html401/index/attributes.html has no attribute "height" for <table> as far as I can tell. Why does WC3 not supprt percentages as height for tables, etc. The problem is not the percentage. You should try using CSS, as discussed here: http://lists.w3.org/Archives/Public/www-validator/2002Mar/0063.html Good luck, -- olivier PGP.sig Description: This is a digitally signed message part

Next Message by Thread: click to view message preview

Re: [VE][108] Error Message Feedback

Hello Eric, On Jul 17, 2004, at 3:12, Eric Mantooth wrote: I used your validation program to see how my site was, and I gave me a couple of incorrect errors.  WEll, maybe they weren't incorrect errors, only errors which were not properly explained by the validator. Not knowing which document you were trying to validate I can only give you a guess of what went wrong... Line 19, column 124: there is no attribute "MARGINHEIGHT" The validator most probably also gave you the following explanation: [[ You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. ...]] For example, if you were using HTML401, check that the incriminated attributes were allowed for the particular element you are using: http://www.w3.org/TR/html401/index/attributes.html Do I have to capitalize the marginheight or put quotes around it?  It also did this for marginwidth, topmargin, leftmargin, hspace, vspace, and height. No, you probably don't have to capitalize them. As a matter of fact, depending on the doctype you are using, lowercase is likely to be correct. You should, however, try to see if CSS would allow you to do the styling effects you are trying to achieve, without using forbidden attributes. I also was wondering what the "ALT" attribute was- it gave me MANY errors because I didn't have it. alt is an "alternate text", required for e.g images. see http://www.w3.org/TR/html401/struct/objects.html#adef-alt Good luck -- olivier PGP.sig Description: This is a digitally signed message part
Sign up for updates to this mailing list. email:
Loading Comments...
Home | News | Patents | Sitemap | FAQ | advertise

Advertising by