We found that if the table depth was more than 5 or so AND the table at
that depth was sufficiently complex (lots of rows and lots of internal data)
that Netscape actually crashed consistently. Either it crashed, or froze
indefinately. Of course, IE had no problem with it... *sigh*
The moral of the story is... flatten out tables as much as possible.
Tony
-----Original Message-----
From: James Hays [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 09, 2001 9:46 AM
To: Orion-Interest
Subject: Re: R: Why is Netscape slower with Orion?
This is because netscape's ui is based on parsing XML every
time is has to
render. What a pain in the butt. Who thought of that?
> From: Marco Isella <[EMAIL PROTECTED]>
> Reply-To: Orion-Interest <[EMAIL PROTECTED]>
> Date: Fri, 9 Feb 2001 14:58:19 +0100
> To: Orion-Interest <[EMAIL PROTECTED]>
> Subject: R: Why is Netscape slower with Orion?
>
> One thing netscape is very very slow at is when it has to
render nested
> tables.. i had a page with 4 level nested tables & with
netscape it was a
> metter of second before the rendering was done; i switched
to a single table
> & the performing was almost acceptable (anyway far slower
than ie).
>
> This was wit ns 4.X, with ns 6 they have speed it up a
little(but still much
> slower than ie).
> Marco
>
>
> -----Messaggio originale-----
> Da: Huibert Aalbers [mailto:[EMAIL PROTECTED]]
> Inviato: venerdi, 26. gennaio 2001 17:58
> A: Orion-Interest
> Oggetto: Why is Netscape slower with Orion?
>
>
> Hi everyone,
>
> Is it just me or has anyone noticed that Netscape is
significantly
> slower than IE when accessing an application built with
orion? Could
> there be anything wrong with my settings?
>
> Thanks,
>
> Huibert Aalbers
> Informix Software
>
>
