The SitePoint Forums have moved.

You can now find them here.
This forum is now closed to new posts, but you can browse existing content.
You can find out more information about the move and how to open a new account (if necessary) here.
If you get stuck you can get support by emailing forums@sitepoint.com

If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Aspen I notice you have underscores. A while ago I had problems with a js function for an open window and it was not working on some browsers. Someone suggested getting rid of the underscores and then it worked. Could have been a coincidence and redoing the code fixed something I missed. I am seeing more stuff advising against underscores in css.

gthorley, the underscores that you mention are part of the file name, so I don't understand why these should be problematic.

Are there any actual instances where underscores have caused you problems. Can you point to any references you've found on the web?

Nonetheless, it is an interesting point. I think I may have encountered a similar quirk in NS6. I'm not sure whether this was to do with underscores in the object IDs I had, or if it was just NS6 misbehaving over the slightest markup error, but it did seem to stumble at certain times when there was no apparent reason for doing so.

I have run intot htis problem many times before, and the only thing I could find out, that if you do not have in your body tag, and onload event, your images will not preload. So you need ot make a call like this for all preloading to occure:

<body onload="PreLoader();">

This will work, as this is what do now for every site I develope and I ahve not problems with the proloading anymore.

This shouldn't matter. If you put your reference your rollovers outwith a JS function in the head of the document, they should automatically load.

I personally use window.onload and call a function initDoc which calls the preload script, that way the graphics load before the body loads. It's meant to be seamless, and yet if the page is trying to load a lot of bytes, or is making many calls to the server, it can time out.

But I don't think, using the onLoad handler in the <body> tag should matter, since I've seen this fail as many times as not - and usually with Dunceweaver's industrial strength code.

I think it's a pity that the quality site that is msdn.microsoft.com/workshop/ should be let down by having no bug list feature. This is something MS could learn from Netscape: a little honesty about their products' failings can really help the developer.

Shame on you! Microsoft software never has bugs. I once received a message from a microsoft person on usenet to a bug I posted in the (then new) version 5 of Outlook Express for Mac explaining that there were no bugs in the software. I should have kept it!

I believe what you might be getting confused about is that from time to time Microsoft previews certain features in their software that are not fully supported yet. As Microsoft brings out newer versions of its software support for these features is further enhanced while new features are added.

Sorry, I have nothing helpful to add to solving the problem. Well maybe I do...

I am not very experienced with JavaScript so it is not natural to me (yet). However, in most languages you are required to declare your variables. Perhaps this is so with IEs implimentation of JavaScript?

If these variables have not been declared elsewhere perhaps you could try this:

var beige1=new Image(120,35);

etc... Of course I'm assuming that that block of code is in global scope, otherwise you would declare the variables in global scope.

OK ... so I went of and did some reading and technically you don't need to explicitly declare variables (I always do because of my C++/Java background) - but I would give this a go to see if it solves your problem.