On Sun, 24 Dec 2000 16:10:01 +0000, Don Cox wrote:
> > IMHO the rendering of a page before its contents have been completely
> > read is an important feature of web browsers which should stay that
> > way.
> You could have it that way if you want. I'm suggesting that this should
> be optional. As downloads get faster (ADSL, cable, etc) there will be
> less and less need to watch the rendering engine doing its stuff while
> you wait, or try to read text which keeps jumping around every time a
> new image arrives.
> I suppose everyone here is tech oriented. But most web users are not.
The main problem with the scheme of waiting for the complete data to arrive
before displaying the page is that it's too common that it won't work
correctly. On many web sites, you have adverts pointing to other websites
and if one of the picture doesn't come you can wait a long time for the page
to render. There's also the problem that some sites don't specify the size
of the pictures (yes, even in 2000). The new rendering engine of V is
designed to handle incremental rendering whenever possible (but this is
perfectible of course, there are still some quirks left). V also tries to
optimize the rendering depending on the speed at which the data comes in.
--
David Gerber
VaporWare programmer
http://www.vapor.com/
finger [EMAIL PROTECTED]
_____________________________________________________________________
Voyager Mailing List - http://v3.vapor.com/
Voyager FAQ....: http://faq.vapor.com/voyager/
Listserver Help: mailto:[EMAIL PROTECTED]?Subject=HELP
Unsubscribe....: mailto:[EMAIL PROTECTED]?Subject=UNSUBSCRIBE