Re: Client control of objects

> It depends on the context. An ideal browser would allow one to
> differentiate between objects that are loaded inline and one's loaded
> manually by following a link.

Among other things.

> Netscape has an option where you can disable loading inline images
> but click on something to load them for a page.

Most browsers don't have enough options for image loading (or most
other things, for that matter). For instance, people said that
browsers should have an option to disable the automatic
loading/playing of background sounds. My response was "don't they all
have that?" I don't run either of the big two on anything with a sound
card, so hadn't really noticed. AWeb (the browser I run most often on
a desktop computer) has a checkbox for "Use background sound", right
under the one for background and colors.

> What's lacking in the OBJECT element is a (recommended) method for
> deciding which objects to load which also takes into account
> bandwidth and connection, or user preferences (I may prefer the way
> my system handles .wav files rather than .au files, and would rather
> play .wav over .au if available, for instance).

Right. But you want MORE information than just the type for making
this decision. Once again, AWeb has THREE image loading options: the
standard do/don't, and "maps only", which download graphical elements
that send mouse coordinates to the server when clicked. Something
similar is probably wanted for <OBJECT> as well, like "Download the
smallest object that encloses any/all links". 

Unfortunately, browser venders seem to be driven by authors, not
users. It's not in the authors best interest for the user to have lots
of options, as they make it less likely the the authors presentation
will come through properly.


Received on Thursday, 11 September 1997 13:47:01 UTC