View Full Version : Ultimate Fade-In Slideshow (v1.5) & chrome

08-11-2010, 08:09 AM
1) Script Title: Ultimate Fade-In Slideshow (v1.5):

2) Script URL (on DD):

3) Describe problem:
website: www.tamar-avni.com (http://www.tamar-avni.com) The slideShow dosen't work on Chrome. the CSS validats and the html validation has errors refering to the js. trying to "fix" them made no deference, the code dosn't work.

4) an intresting fact about viewing this site in Chrome is that the inner pages work perfectly with all the DD scripst most of the time and on most PCs, but sometimes (and aspecialy on the customer's PC) the script doesn't work. the page is visible but not the images that should be desplayed by the script.
I'm ageing fast trying to solve this... please help.

08-11-2010, 10:18 AM
Use the current version:


Or, if you are unwilling to make such a change, here's a link to an interim version (v1.51a) that takes care of that problem, but otherwise works just like v1.5:


08-12-2010, 06:31 AM
Thanks for the rapid reply!
I've changed to the new script. explorer doesn't mind, it works fine.
His majesty Chrome doesn't except...it seams the div is not visible to chrome. all that I see is a small section of the dotted border of the div's containing td, althogh it has dimensions in the css.
any idea?

08-12-2010, 08:34 AM
Looks like some kind of a character encoding issue. Even though you have:

<META http-equiv=Content-Type content="text/html; charset=windows-1255">

The page is being served/seen by Chrome (and Firefox and Safari) as UTF-16. Apparently so is the script, which makes it look like Chinese or some other Asian pictographic language.

This may be due to the server's configuration, which generally is the only way to override the page's meta tag encoding. Though this can be done several ways on the server.

However, I have a hunch that it's because the page itself was saved in UTF-16 in your editor, this is also known as UCS-2 Big (or Little) Endian.

Ideally the page should be saved in the encoding it is being served as. This can be done in several editors. I'm only familiar with how in one, NotePad++.

If you don't know how to do this in your editor (save as windows-1255), I can attach a version of your page that is saved in that encoding. But a more common encoding is UTF-8, which is available in a great many more editors and will also work for the Hebrew characters you have in the meta description tags. If you save in UTF-8 encoding, then change the meta tag:

<META http-equiv=Content-Type content="text/html; charset=windows-1255">


<META http-equiv=Content-Type content="text/html; charset=utf-8">

Also Important: You may not be able to convert your current file. You may need to make a new file in the proper encoding. To that end, I'm attaching a properly encoded version in a .zip archive:


08-14-2010, 07:35 PM
Thanks John for your deep replay.
I wonder though, when I first uploaded the site to the server, I had some rendering problems and the server support insisted I should upload in unicode. that worked and I re uploaded the site in unicode. can this be the conflict you refer to or is it a different issue?

08-14-2010, 11:45 PM
It's the same issue.

If you have little endian like I'm beginning to think you do, on your copy (not the one from my post), change:

<META http-equiv=Content-Type content="text/html; charset=windows-1255">


<META http-equiv=Content-Type content="text/html; charset=utf-16l">

You used unicode 16 which has l and b (little endian and big endian). Using unicode 8 is probably what they meant (utf-8). But using windows-1255 should also work if the page is saved that way.

The thing is, whatever you use, the page must be saved in that encoding in the editor and its meta Content-Type tag must specify the same encoding that it was saved in.

But, due to the way different browsers react, the best idea would probably be to save in utf-8 (which is also unicode) and use this meta Content-Type tag:

<META http-equiv=Content-Type content="text/html; charset=utf-8">

08-15-2010, 04:36 AM
Thanks John!
It works!
You have been a grate help!
You think if I change the encoding on all pages the inconsistency of the rendering of the different pages will also stop?

08-15-2010, 08:38 AM
As long as the markup and styles are consistent, yes. Having the same encoding on all pages would also be a good idea.

You should however keep backups of what you have, just in case you run into problems. You cannot always be guaranteed to be able to easily switch the actual encoding of the page back, though in theory you can.

08-15-2010, 12:33 PM
Thanks so much for all your help. it looks like all is well now. I hope the site will not start to act differently later like it did befor...
:) thanks again,