Jörn,
>Its all a bit tricky: Those portlets are enclosed in about 6 layers of
>tables (gah) and IE doesn't even let me start the debugger, it simply
>fails completely to display anything at all.
I really think it's the tables that are your problem. IE has some issues
trying to manipulate element
>>IE completely refuses to load the page at all,
instead alerting me about something like "can't display this page", so
quite impossible to debug.
This sounds like the weird bug in IE when you modify the dom before
the page is ready. Something on msn developer about this.
MarcosBL schrieb:
Same issue here, i solved it just using gzip... not only it increases
speed (compresion of html up to 85%) but it solves the problem because
the html is fully loaded when it reaches the js execution.
Thanks all for your suggestions, I'll give them a try.
Its all a bit tric
Same issue here, i solved it just using gzip... not only it increases
speed (compresion of html up to 85%) but it solves the problem because
the html is fully loaded when it reaches the js execution.
On 3 abr, 01:08, Klaus Hartl <[EMAIL PROTECTED]> wrote:
> Jörn Zaefferer schrieb:
>
>
>
>
>
>
>
Jörn Zaefferer schrieb:
Hi folks,
I'm trying to solve a severe performance issue I'm experiencing in an
enviroment that heavily uses incremental page rendering. I have several
parts on one page that are basically independent, but to apply any
JavaScript to one of those parts (actually jsr16
L PROTECTED]
> -Original Message-
> From: jquery-en@googlegroups.com
> [mailto:[EMAIL PROTECTED] On Behalf Of Geoffrey Knutzen
> Sent: Monday, April 02, 2007 3:47 PM
> To: jquery-en@googlegroups.com
> Subject: [jQuery] Re: Dealing with incremental page rendering
> and
: [jQuery] Re: Dealing with incremental page rendering and ready
events
To simulate low bandwidth, you might be better off using throttling
software on your local machine and crank it up to 11.
For IE debugging, does the web developer extension not help?
--Erik
On 4/2/07, Jörn Zaefferer <[EM
To simulate low bandwidth, you might be better off using throttling
software on your local machine and crank it up to 11.
For IE debugging, does the web developer extension not help?
--Erik
On 4/2/07, Jörn Zaefferer <[EMAIL PROTECTED]> wrote:
Hi folks,
I'm trying to solve a severe performan
2007/4/2, Jörn Zaefferer <[EMAIL PROTECTED]>:
Hi folks,
I'm trying to solve a severe performance issue I'm experiencing in an
enviroment that heavily uses incremental page rendering. I have several
parts on one page that are basically independent, but to apply any
JavaScript to one of those pa
Hi.
I can't give much super targeted help with the info you provide. I have a
couple thoughts that may or may not be helpful.
Although there are exceptions, usually javascript that fails because the page
is not loaded will still fail even if your network connection is very fast (in
other wor
Jorn,
I've created Progress Meters that worked in IE/FF before that used
incremental page loads to update the meters--so I know it's not a FF issue
(the code was non-jQuery related.)
However, I could see if your code is inside a tag or something
where FF might have problems.
-=Dan
>-Origi
11 matches
Mail list logo
