|
|
Posted by David Mark on 10/29/07 11:34
On Oct 29, 4:25 am, Bone Ur <bon...@example.com> wrote:
> Well bust mah britches and call me cheeky, on Sun, 28 Oct 2007 08:57:45 GMT
> David Mark scribed:
>
> >> You can j/s preload sequentially: ie, not starting the following preload
> >> until the previous is finished. I've done that and it works. But a
> >> better idea (I think) is just to make a position:absolute;
> >> visibility:hidden; div "layer" encompassing all the images which won't
> >> show because of the css.
>
> > That will mess up the semantics of the page and will look strange when
> > style is disabled. For the scriptless approach, it is better to use
> > background images.
>
> Background images don't always load as one might wish, though. The
I don't know what you mean by that. But the typical need for
preloading is for rollovers and the like, so it isn't a catastrophe if
the images fail to preload.
> styling-disabled is a valid concern, but despite conventional mythology,
> styling is necessary nowadays and anyone who disables it except for testing
That is only part of it. Some agents don't support style at all.
> is a moron. As for semantics - phffft! Very few pages have correct
It is not the users' fault if a document is poorly designed.
> semantics, anyway, and a sequential list of links in a "layer" will
Very few pages are written by competent Web developers.
> certainly not mess them up if they are correct.
What list of links? The suggestion was for a "layer" with hidden
images. Search engines, screen readers, style-challenged agents, etc.
will have no idea what to make of such a thing.
Navigation:
[Reply to this message]
|