Ultimate Fade-In Slideshow, my page doesn't validate

**TequilaMB** · 11-15-2008, 10:22 PM

1) Script Title: Ultimate Fade-In Slideshow

2) Script URL (on DD): http://www.dynamicdrive.com/dynamici...nslideshow.htm

3) Describe problem: Page doesn't validate, has many errors. Did I do something wrong?

**jscheuer1** · 11-15-2008, 11:04 PM

Yes, a number of things. Also, the script 'as is' will not validate (though it can be made to do so), for that part the best course is to make it external. When you do, be sure to follow DD's TOS:

usage terms

specifically including the script credit on your page.

However, I must say that after removing the script from a local copy of your page, there were still the exact same number of errors, the type and kind of which lead me to believe that you are not generally in the habit of validating your work.

Is this true?

In any case, if you want help validating your page aside from this script, you should have posted in the HTML forum. Since we already have an open thread on this though, I will have a look see if I can correct those 13 errors and get back to you.

One thing I can say right now is that XHTML is a poor choice of DOCTYPE, as - if your page were truly served as application xml/XHTML, Internet Explorer would not display it.

**jscheuer1** · 11-15-2008, 11:17 PM

Here you go:

Attachment 2218

Not bad, average time 1 minute per error, and that includes archiving and uploading the result.

**TequilaMB** · 11-16-2008, 12:50 PM

Nice John! I'm impressed. Later I will compare to see how you fixed those.

The only remaining issue is that the left table background image - which acts as a filler beneath the nav buttons, allowing the content table to expand or contract as needed, is not showing in the new version. I uploaded it with a new name to the server:

http://auburndowntown.org/Home5.htm

Is there an easy fix (without re-introducing the errors)?

**jscheuer1** · 11-16-2008, 01:42 PM

Change the two instances of:

Code:

background-image:url(Images/Buttons Sliced/FillBar.jpg);

to:

Code:

background-image:url(Images/Buttons%20Sliced/FillBar.jpg);

In my haste I didn't notice the space in the path name, which requires either quoting the value, or as I am choosing to do, using %20 to represent the space.

**TequilaMB** · 11-16-2008, 05:46 PM

Done. And now it looks fine.

I have to confess, however, that the errors that related to the Slide-show script had graciously already been fixed by my webhost guru prior to your seeing that validation page. Before that, it had something like 23 errors. But I thank you for your assistance in fixing the rest!

I have much yet to learn . . . all in the fullness of time.

**TequilaMB** · 11-17-2008, 05:17 PM

John,

I've followed the directions for putting the slideshow in an external file. (I've also changed the path for the rollover buttons to eliminate the space).

I uploaded the result http://auburndowntown.org/home6.htm and two things are happening:

1) I'm getting four new validation errors
that don't appear in the previous iteration of the page; and

2) The

Code:

style="margin-top:0;"

doesn't appear to be functioning, although it is in the page's code.

I don't know where I've gone wrong. Can you help?

**jscheuer1** · 11-17-2008, 05:41 PM

This:

Code:

<script src="slideshow.js" type="text/javascript"></script>
/***********************************************
* Ultimate Fade-In Slideshow (v1.5): © Dynamic Drive (http://www.dynamicdrive.com)
* This notice MUST stay intact for legal use
* Visit http://www.dynamicdrive.com/ for this script and 100s more.
***********************************************/

should be:

Code:

<script src="slideshow.js" type="text/javascript">

/***********************************************
* Ultimate Fade-In Slideshow (v1.5): © Dynamic Drive (http://www.dynamicdrive.com)
* This notice MUST stay intact for legal use
* Visit http://www.dynamicdrive.com/ for this script and 100s more.
***********************************************

</script>

Because of that, it looks to the validator as if you are starting the body early. Which is what (most likely) gives rise to the other errors, including the apparent lack of 0 margin. But the margin really is 0 at least in some browsers, it's just that the out of place comment is there invisibly at the top of the page taking up space.