Forum Moderators: open
Line 12, Column 58: there is no attribute "BACKGROUND".
<table border="0" width="85%" cellspacing="0" BACKGROUND=fantasy9bk5.jpg cellpadding="25">
To use it within the HTML:
<table border="0" width="85%" cellspacing="0" style="background: url(fantasy9bk5.jpg);" cellpadding="25">
However you should research how to do it with a class in externally linked stylesheet.
Line 36, Column 73: there is no attribute "BACKGROUND".
…="0" CELLPADDING="1" WIDTH="45%" BACKGROUND="fantasy9bk3.jpg">
errors are as follows
Line 96, Column 66: reference not terminated by REFC delimiter .
…y Designed By Glamorous Creations, Copyright (©-2008-2009)</p> error
If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 182, Column 4: end tag for "ul" which is not finished .
</ul> error
Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>
Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists (ul, ol, dl) require list items (li, or dt, dd), and so on.
Line 96, Column 66: XML Parsing Error: CharRef: invalid decimal value .
…y Designed By Glamorous Creations, Copyright (©-2008-2009)</p> error
Line 96, Column 66: XML Parsing Error: xmlParseCharRef: invalid xmlChar value 0 .
…y Designed By Glamorous Creations, Copyright (©-2008-2009)</p> error
thank you id like some help fixes these.
The ul error is also described in the error text - your code has something wrong between the <ul> and the </ul> tags - either it forgets to close some tag that was opened after the <ul>, or possibly it doesn't have any <li> elements at all.
...why do i have to use the balidator thing its useless.
Well, it does tell you if there are any errors, and with a bit of experience it pretty well tells you exactly where that error might be and why.
If there are errors in your source then you could well have problems rendering your site cross browser. It's difficult to test in all browsers under the sun; ensuring there are no errors is a good start. Certainly, if you do have rendering issues (may be just in some browsers) then making sure there are no errors is the very first thing to do.
For instance, you are lucky that most browsers are interpreting your © ok, since you are following it with a non-numeric character '-'. But, if you wanted this to come immediately before the '2008' you would have problems, having missed the trailing semi-colon ';'. What if the text that came after the © was dynamically pulled from a DB (as many people do seem to update there copyright information each year)?
.... why do i have to use the balidator thing its useless. and its alot of trouble for most.....
It's already shown you how useful it is. You learned that when you use an entity, it must begin with & and end with ;, right?
Another thing about the W3C validator is that errors can cascade. You may only have one error but that one causes it to misinterpret elements farther down the page that are NOT errors. So hit the first ones, look for other suspects, and revalidate.
Stick with it, years from now when someone looks at your pages, they will have less to pick at to say what's wrong with it. :-)
