So, if I got you right, the benefit of using the workaround with the
deferred command, is just, that the user is presented with the new
page first: and then she has to wait for the 4.5 sec.
I'd rather disable the history tokens at all and present the users
with a 'set current-URL' button or smth.
We experienced a very similar problem, though we're not using GXT.
Doing a navigation in IE was taking a crazy amount of time, whereas in
other browsers the navigation was fine.
We wound up doing the navigations by getting the user
"gesture" (click, or whatever) indicating that they want to navig
Hi,
we have a very strange performance problem especially in context with
history handling and IE6 / IE7
Our application is based on GXT and is already a rather large one (1.6
MB).
On less powerfull computers (e.g. Netbooks -> Asus EEE 1000h) the
performance of history handling is really bad (c
