I thought about doing that, but I wasn't convinced I could rely on all
browsers leaving the page visible until it received content for the
next page. Have you used this in IE 6 and 7, Firefox 1.5 and 2, and
Safari 2 by any chance? If not, I guess I'll check it out. It's
probably more typing than
It's probably more typing than my solution because of the number of
onClick handlers I'll have to add
Not sure if you can do it in your context, but instead of calling the JS
function in all buttons onClick, you could just call it in the FORM
onSubmit...
On Thu, 2006-12-07 at 03:45 -0800, Sam Gendler wrote:
I thought about doing that, but I wasn't convinced I could rely on all
browsers leaving the page visible until it received content for the
next page. Have you used this in IE 6 and 7, Firefox 1.5 and 2, and
Safari 2 by any chance? If not,
On 12/7/06, Fred Janon [EMAIL PROTECTED] wrote:
It's probably more typing than my solution because of the number of
onClick handlers I'll have to add
Not sure if you can do it in your context, but instead of calling the JS
function in all buttons onClick, you could just call it in the FORM
To avoid making multiple changes you could wrap your @Submit component
into a @CustomSubmit which passes all informal parameters and add's the
onClick and then overwritting the @Submit with @CustomSubmit in
the .application (worked in 3.* don't know about 4.*)
Len
www.len.ro
On Thu, 2006-12-07
Unfortunately, my problem is that I need it on plain links as well as
in forms. Nothing I can't fix by just assigning a new class to any
link that needs the handler and then adding the handler via a
javascript method which iterates over all elements with the
'pleaseWait' class.
--sam
Sounds
if you can get the first bytes of the second (slow) page loaded you can
start that page with the html for a div to appear in the centre of the
screen in front of the real content.
The last thing on the page should be the html which moves this either away
to the left (negative coordinates) of
On 12/6/06, Jesse Kuhnert [EMAIL PROTECTED] wrote:
It's hard to tell which problem you are trying to solve through your comments.
Well, I've got a lot of pages that just plain take a while (1-2 secs,
with a max at maybe 5 seconds for one particularly nasty page that
will eventually get some
