Hi,
I have checked the 1.4-rc2 or 1.3.6, and have not seen this patch. Can
anyone please confirm the exact release in which this issue is fixed.
Thanks
Kuga
--
View this message in context:
http://www.nabble.com/wicket-ajax-and-IE-performance-problems-for-pages-with-many-links
> tags in the page markup.
*
*
* For background information, see http://www.nabble.com/wicket-ajax-and-IE-performance-problems-for-pages-with-many-links-td23078336.html";
* >this mailing list thread
*
* This behavior simply makes sure that our patch gets applied to wicket-ajax.js
* (b
Wicket.Focus.attachFocusEvent is very slow in IE compared to FireFox.
At first I thought attaching an event was slow, but it seems to be just
iterating over the list of elements returned by
document.getElementsByTagName takes forever.
FF would take 17 ms, IE 900ms for a test page with 1200 lin
tags in the page markup.
> *
> *
> * For background information, see href="http://www.nabble.com/wicket-ajax-and-IE-performance-problems-for-pages-with-many-links-td23078336.html";
> * >this mailing list thread
> *
> * This behavior simply makes sure that our p
2009/4/17 Peter Gardfjäll :
> Sure,
> here goes. I have added both the java and the js file to the same Java
> package:
You da man! Thank you very much! That's a pretty slick trick you did
by extending the ajax behavior superclass so that the ajax javascript
files get included before yours. I'
{...@link Page}s that need to
prevent
* the page load performance penalty incurred when wicket-ajax.js traverses
all
* <a> tags in the page markup.
*
*
* For background information, see http://www.nabble.com/wicket-ajax-and-IE-performance-problems-for-pages-with-many-links-td23078336
all
* <a> tags in the page markup.
*
*
* For background information, see http://www.nabble.com/wicket-ajax-and-IE-performance-problems-for-pages-with-many-links-td23078336.html";
* >this mailing list thread
*
* This behavior simply makes sure that our patch gets applied to
Did that code actually work for you? I tried adding this js, but i
couldn't get it to show up in the correct place. And, when I did, it
didn't seem to improve much. Care to share your code?
2009/4/17 Peter Gardfjäll :
> I have written a simple WicketAjaxJsPatch Behavior which simply adds
> the
I have written a simple WicketAjaxJsPatch Behavior which simply adds
the aforementioned javascript to the page.
In our application, we have several pages that suffer from the same problem.
It would be tedious to have to update all of these pages one-by-one.
So is there any way for me to add this Be
Well, it kinda does. You can submit the links and buttons with
keyboard - and when you do it does make sense to preserve focus when
you replace the submitting button or link.
-Matej
On Fri, Apr 17, 2009 at 9:48 AM, Johan Compagner wrote:
> Buttons and links dont make much sense yes.
> Dont reme
Buttons and links dont make much sense yes.
Dont remember why we should do this.
Will check the code
On 16/04/2009, Igor Vaynberg wrote:
> this code is there so we can track focus and properly restore it after
> ajax modifies the dom. i am not sure why we need to track and restore
> focus on anch
Thanks Igor,
the suggested workaround seems to work fine. However, it is not enough
to just override the attachFocusEvent function -- you also need to
deregister the previously registered function. I did as follows (I
apologize for the lack of elegance, I'm not a js expert):
if (typeof(Wicket) !=
you can try adding this to the head after wicket-ajax.js
So, we understand what's slowing us down? Any way to turn that stuff
off on our end to get stuff working? I've got a release going out the
door that's slow as heck on IE right now.
On Thu, Apr 16, 2009 at 12:03 PM, Igor Vaynberg wrote:
> this code is there so we can track focus and properly res
this code is there so we can track focus and properly restore it after
ajax modifies the dom. i am not sure why we need to track and restore
focus on anchors, it is only important when you are typing so that the
cursor doesnt move elsewhere - so only for textfields and textareas.
johan, matej says
Hi James,
I'm pretty sure that links are part of the problem.
To verify this, try replacing all tags with e.g. and see if
you can spot any difference in response time.
Alternatively, try replacing/commenting out ajax components/behaviors
on your page to prevent wicket-ajax.js from being pulled i
Peter,
I have experienced similar problems just recently. I didn't narrow it down
to the fact that the links were the problem, as you have, though! I have
been racking my brains trying to figure this thing out. My page is similar,
a table with lots of cells in them that are links. I've turned o
Hi all,
I am working on a wicket application intended to be executed both on
FF3 and IE7.
While working on this application I have discovered that the rendering
of some pages are a lot slower in IE.
The pages that were significantly slower on IE have a couple of things
in common: they are ajax-ena
18 matches
Mail list logo
