Email address obfuscation in effect -- please
click here to turn it off.
[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
Mike Miller wrote:
>
> On Wed, 1 Aug 2001, Marcus Semanek wrote:
>
> > Actually it only appears to load them faster than netscape since it
> > renders the page as it comes in while netscape waits for the entire
> > page to load and then does the rendering.
>
> I'm sure that's it. So you're saying that the complete page is finished
> just as quickly in Netscape as in IE. I usually don't want to wait for
> every little bit of a page to be downloaded before I start to read it.
> Therefore, I think the IE strategy is better. Is there a downside I'm not
> understanding?
>
> Mike
The downside is that you never know what will load next as you're
displaying the page. So if you have code that requires closing tags that
are never received, you have to make up your own tags or "loosen" the
HTML standard's implementation in your rendering engine. That's what MS
did, I bet. Basically, no strict adherence to the standard for you.
--
Misha Kovalenko
Webmaster Columbia College
Tel.: 573-875-7314 1001 Rogers
Fax: 573=875=7320 Columbia, MO 65216 USA
--
To manage your subscription, go to http://mlug.missouri.edu/members/edit.php
Archives are available at http://mlug.missouri.edu/list-archives/