Forum Moderators: open
<body onLoad="MM_preloadImages('../images/graphical_links/top_nav/images/home_01-over.gif','../images/graphical_links/top_nav/images/directions_01-over.gif','../images/graphical_links/top_nav/images/store_hours_01-over.gif','../images/graphical_links/top_nav/images/order_01-over.gif','../images/graphical_links/top_nav/images/contact_01-over.gif')">
Purple - right you are, it's a browser function (my breaks were coming after slashes, not hyphehs)
I often need to edit the code pasted in on the forum to get it to break somewhere so we avoid horizontal scrolling, and I made a wrong assumption.
I suppose the idea of preloading images after the document has loaded is that the images aren't visible in the initial rendering of the page, so why use up bandwidth while the main page load is occurring.
However, I often preload rollover images right in the head, or as the last bit of code before the </body> tag - to no detriment that I can see. But DW prefers to do the preloads "onLoad", which really is a hair better, especially for very "fat" pages
<body onload="preloadImages();">
Anything else that would be in the <body> and even the <head> tag goes into external .css or .js.
I'm just trying to provide the quickest route from point a to point b! ;)