|
pageoneresults -> RE: extra space between tables (9/12/2002 22:55:23)
|
> Actually, the DTD statement I am using is the one you recommended without the http part. Should I be using a different one? I' ve read a lot about it, but still can' t figure it out. You' re fine with the one you have. I use ImageReady also and have no major problems with the preload script. I did put mine into an external .js file and call it into the page from the <head> of my page like this... <script type=" text/javascript" src=" http://www.seoconsultants.com/javascript/seo-consultants.js" ></script> I noticed that you have two scripts coming in. One that resides in your head and another that is in an external file. Why is that? You should put all of it in the external file and make sure that you have the above script tag in your <head></head>. P.S. No, you do not need the language attribute, it is now deprecated. If you don' t know what it is, then don' t worry about it just yet. As long as your script tag looks like the above, of course with your file reference, you' ll be okay. I also noticed that you have image references like this in your javascript... biooxmenu_01_save_over = newImage(" biooxmenu_01-save_over.gif" ); Are your images all floating in the root level of your directory? Or are they inside of a sub-directory labeled images? Your external file shows image calls like this... ../images/colortabs_01-cleaner_over.gif" ); Since I can' t see the directory structure of the site, I can only assume based on the code I' m able to access. Don' t want to download your whole site at the moment! Get rid of the ../ in front of the ../images/ directory path. You don' t need the .. and it causes various problems with the rollovers depending on where in the directory structure your files are. If that first piece of javascript in your <head> section has the wrong path for the images, then you need to update your javascript and provide the correct path, i.e. biooxmenu_01_save_over = newImage(" /images/biooxmenu_01-save_over.gif" ); Although I don' t think that is a problem, you would have broken images on rollover state. You should keep all of your images in one directory at the first level... http //www domain.com/images/file-name.gif This way you can use the /images/ path and never have any image referencing problems in your javascript or html, no matter where in the directory structure you are. You will also need to update all of the references in the rollover code that is in your <body>. Using the FP Find and Replace feature works wonders in these instances.
|
|
|
|