Forum Moderators: open
0015:<Meta http-equiv="Content-Type" content="text/html;charset=iso-8859-1">
0016:[1]^<script language="JavaScript">
----:[1]^Warning: tag <script> missing required attribute "type". Click here to learn more
----:[1]^Hint: use "type" attribute with "language" attribute
0017:<!--
here is the big one,
<body bgcolor="#FFFFFF" text="#000000" ----:[1]^Warning: <body> proprietary attribute "leftmargin". ----:[2]^Warning: <body> proprietary attribute "topmargin". ----:[3]^Error: unsupported attribute "marginwidth" for tag <body>. ----:[4]^Error: unsupported attribute "marginheight" for tag <body>. [1][edited by: tedster at 2:39 am (utc) on Dec. 14, 2002]
^leftmargin="0" [2]^topmargin="0" [3]^marginwidth="0" [4]^marginheight="0"
onLoad="MM_preloadImages('pictures/buttonsover_01.gif','pictures/newover_01.gif',
'pictures/newover_02.gif','pictures/newover_03.gif','pictures/newover_04.gif',
'pictures/newover_05.gif')">
Click here to learn more
----:[1]^NOTE: "leftmargin" with <body> is compatible with all selected browsers.
Click here for Browser Compatibility report
Click here to learn more
----:[2]^NOTE: "topmargin" with <body> is compatible with all selected browsers.
Click here for Browser Compatibility report
Click here to learn more
----:[3]^NOTE: "marginwidth" with <body> is NOT compatible with all selected browsers.
Click here for Browser Compatibility report
Click here to learn more
----:[4]^NOTE: "marginheight" with <body> is NOT compatible with all selected browsers.
Click here for Browser Compatibility
[edit reason] stop horizontal scroll [/edit]
pageoneresults,
Thanks! Does leaving out the language declaration affect older browsers like NN4.x?
Jim
Does leaving out the language declaration affect older browsers like NN4.x?
Not that I'm aware of. I test regularly with NN4.78 and have not seen any issues with my javascript. I don't utilize any hard core javascript so I cannot accurately answer that question.
In regards to the above error with margins, if you are using css, here is the solution. Strip everything you can from that <body> tag. I usually just end up with my onload event in the <body>.
body {
position:absolute;
top:0px;
left:0px;
margin:0px;
padding:0px;
}
I don't know where i went wrong on this one. please help again
0004:<Meta name=”description” content=”Need (1)^help (2)^building (3)^search (4)^engines (5)^friendly (6)^web (7)^site?”>
----:(1)^Error: unknown attribute "help" for tag <meta>. Click here to learn more
----:(1)^NOTE: "help" with <meta> is NOT compatible with all selected browsers. Click here for Browser Compatibility report
----:(2)^Error: unknown attribute "building" for tag <meta>. Click here to learn more
----:(2)^NOTE: "building" with <meta> is NOT compatible with all selected browsers. Click here for Browser Compatibility report----:
... and so on, right through every word in the description meta tag.
[edited by: tedster at 3:29 pm (utc) on Dec. 15, 2002]
1) It looks like you may be using the wrong quote character - Try editing your page with a simple text editor like NotePad and make sure you are not using special left double quote and right double quote symbols. It could also be a declared-versus-actual character set problem. Compare to this sample:
<meta name="Description" content="The finest in fuzzy blue widgets for all occasions.">
2) Very often, a single problem or error will cause a cascade of error reports. That is what is happening here. Don't worry about the number of problems, just look for the first possible cause of the problem.
Jim
[edited by: tedster at 3:20 pm (utc) on Dec. 15, 2002]
Another error that I see quite regularly, but not here, is the use of an XHTML-style closing slash "/" inside tags, being incorrectly used in an HTML document, especially on META tags, like:
<head>
<meta name="Description" content=" Your Description Here. " />
<meta name="...
This has the unfortunate effect that the first slash "/" encountered after <head> is interpreted as </head><body> so giving errors for the rest of the meta tags within the head section, as they are now seen to be within the <body> section. Further errors are then given for the real </head> and <body> tags, as these are now flagged as being duplicates.
You can test this by taking a validated HTML 4.01 web page, adding the extra / on an early META tag in the list, then revalidating the page using the service at [validator.w3.org...] , noting the new error list, as well as inspecting the Parse Tree with the now misplaced and additional tags.
[edited by: g1smd at 10:21 pm (utc) on Dec. 15, 2002]
An other issue is with the characters. I get the following, "Found an invalid entity "•". Characters between 128 and 159 (inclusive) are reserved for control characters in the standard Internet character sets" Could I replace it with <b><li></b>?
I don't think that code would be valid. A list item is an HTML element that makes sense only within the context of a list (i.e. ul or ol), and you wouldn't boldface it any more than a margin or horizontal rule.
For 4th generation and newer browsers, • should work for a bullet or · for a small bullet ("middle dot"). You could also use an image.
@benwalsh: buttonType is not a valid attribute for <span>.
[edited by: choster at 11:11 pm (utc) on Dec. 30, 2002]