View Full Version : DOCTYPE with JS

01-05-2011, 05:21 PM
Hey, might be a stupid question, but which is the best DOCTYPE to use with JavaScript?

Just validating now and its telling me that the<body onLoad="startclock()"> onLoad attribute is not supported....

Anyone understand what it's asking me to do?


01-05-2011, 05:40 PM
<!doctype html>

01-05-2011, 05:46 PM

I'm using XHTML 1.0 Transitional...:)

01-05-2011, 05:58 PM
afaik, JS is not interested in the doctype. a DTD is just a Node in the DOM tree and the DOM tree is made by the browser’s JavaScript engine.

01-05-2011, 06:00 PM
Do you understand what it is telling me to do then?

# Error Line 133, Column 14: there is no attribute "onLoad"

<body onLoad="startclock()" background="lovelywaterfall.jpg">

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. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

If no luck i'll send my code over.


01-05-2011, 08:55 PM
if you use an XHTML doctype, the document becomes case-sensitive. thus onLoad != onload. Element attributes are all lowercase in XHTML.

01-05-2011, 10:21 PM
Ah thank you very much! Error gone.

I'll keep that in mind. :thumbsup: