Sliced images - why ?

by "John Aitchison" <jaitchis(at)hwy.com.au>

 Date:  Sat, 16 Mar 2002 11:19:53 +1100
 To:  hwg-basics(at)hwg.org
  todo: View Thread, Original

tthis is a newbieish (?) question .. I can't quite grasp why you would 
use sliced images. From googling, the claimed benefit seems to be 
faster loading, but my experience (as a user) seems to be that you 
get a whole bunch of ugly holes that fill in a random fashion (giving 
no impression of faster loading).

Also,I am not sure that preloading images works . If you look at this 
site http://www.mkdata.dk/wg/slice01/ekke.htm
you will see that the onload event handler for the body tag is 
supposed to get all the images needed. Well it does not seem to 
work on my machine (as in, it appears that the image slices are 
being downloaded 1 at a time and the cells in the table being filled as 
they become available). And even if it did work, what would be the 
point - you would still have to wait for all the slices to come down 
before the image was composed, in which case why not send the 
image unsliced.

I suppose you can easily have different alt text for each image slice, 
but you can do that with USEMAP : I suppose you could assign 
different event handlers for each slice .. dk if I want to do that.

confused AGAIN <g>

HTML: hwg-basics mailing list archives, maintained by Webmasters @ IWA

This page is part of a preserved archive of archives.hwg.org. The site is no longer active and its content is not maintained. For enquiries about this archive, write to archive(at)iwanet.org.