[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: Preventing second click

Subject: RE: Preventing second click
From: <Trish@xxxxxxxxxxxxxx>
Date: Thu, 28 Sep 2006 08:03:09 -0400
on second click
You can also try something like this:

<input type="image" src="{$varContinueBtn}" value="submit"
onClick="this.style.display='none'; divProcessingText.style.display=''"
border="0" alt="continue" name="btnSubmit" id="btnSubmit" width="125"
runat="server" /><span id="divProcessingText" style="display:
none;">Processing...</span>

Hope this helps!
Trish

-----Original Message-----
From: Geert Josten [mailto:geert.josten@xxxxxxxxxxx]
Sent: Thursday, September 28, 2006 7:15 AM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: RE:  Preventing second click

Hi Oleg,

I think your method is in principle right. Disable the button on the
HTML page as soon as it is clicked. Though you don't need the onload
part. You generate the HTML yourself, so by default it should be enabled
and only clicking it will disable it.

About the XSL 'parent and child' files, that should not be of concern.
You generate one HTML file to which the several XSL's each contribute a
part. Just make sure things match in the end result (the HTML page),
that is all you need to care. Besides, dropping the onload part, might
'solve' this, as in that case your javascript only concerns the submit
'button'. :-)

And Yes, you could have asked on the Cocoon list as well.. ;-)

Kind regards,
Geert

> I have a web XSLT application which is (among other things)
> doing large SQL Insert's, so sometimes it takes a while, user
> becomes impatient and clicks again (or just does
> double-click), and the same data is getting inserted again
> creating duplicate rows.
>
> I was thinking of some simple solution in Javascript, something like:
> <input name=myBtn onclick="this.disable=true;" /> and <body
> onload="if (document.myBtn.disabled)
> document.myBtn.disabled=false;" /> ...
> </body>
>
> Do you think that might work ?
> (that input is not a Submit button, the page actually reloads
> when any DB transaction is done)
>
> The complication is that the <body> and <input> are in
> different XSL files, i.e. if the button is in the
> "grandchild" of the <body> form (child xsl:include's the
> parent which includes a grandparent containg the <body>).
> Do they really share a "document" ?
> Doesn't seem to work for me.
>
> Or is there a nicer solution ?
>
> Please advise.  Any help is very appreciated.
>
> Thank you in advance,
> Oleg.
> P.S.: Actually, it's a Cocoon/XSLT application with Actions
> written in Java, but I didn't want to go into that, hoping
> for a simple non-Java solution [without multi-threading and
> other potential troubles].
>
>


Drs. G.P.H. Josten
Consultant



Daidalos BV
Source of Innovation
Hoekeindsehof 1-4
2665  JZ  Bleiswijk
Tel.: +31 (0) 10 850 1200
Fax: +31 (0) 10 850 1199
www.daidalos.nl
KvK 27164984


De informatie - verzonden in of met dit emailbericht - is afkomstig van
Daidalos BV en is uitsluitend bestemd voor de geadresseerde. Indien u
dit bericht onbedoeld hebt ontvangen, verzoeken wij u het te
verwijderen. Aan dit bericht kunnen geen rechten worden ontleend.

Current Thread

PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.