Re: Preventing second click

Play the video

Subject: Re: Preventing second click
From: "Oleg Konovalov" <olegkon@xxxxxxxxx>
Date: Thu, 28 Sep 2006 21:28:04 -0400

I have made some progress and found a few interesting things:
1) I should use just onload="if (btn_id.disabled)", not
onload="if(document.formname.btnname.disabled);" on grandparent form;
That works in FireFox, but not IE6 [which I target],
where I had to use:  if(document.getElementById('btn_Id').disabled)

2) for some reason that always returns false, even if I just set
<input name="name1" id="btn_id" onclick="disabled=true">
(or this.disabled=true )
I have never heard that reloading a page resets any of its attributes and
there are no other buttons with the same id or name.

3) the other strange thing is that I can't use any curly braces in any
onload or onclick, doing:
onload="if (btn_id.disabled) { alert.window('some text'); }" gives error:
Fatal: File SystemId Unknown; Line 16; Column -1; Could not find function:
window.alert
but runs just fine without curly braces
That looks like a problem to me. Any workarounds ?

TIA,
Oleg.

On 9/28/06, Abel Braaksma <abel.online@xxxxxxxxx> wrote:

Oleg Konovalov wrote:
> No, I don't use AJAX or CSS [and not planning to do that].
> What I don't understand why on the "grandparent" form
> I can not get a value for that button declared on its grandchild.
> So for "document.formname.btnname" or "window.document.formname.btnname"
> I get "undefined" on that grandparent,
> for "document.formname.btnname.disabled" I get nothing at all
> [probably causes a Javascript error], no "alert".
>
> What should I do ?

This rather sounds more like a javascript discussion to me than an xslt
discussion, but since it appears to be related in this case, let me give
it a try.

 From your first post, I may have missed some details, or you may not
have mentioned it. You talk about several xslt files making up your html
form. You call it a "web XSLT application", which I translated as an
application doing client side xslt transformation. Reading your post
again, I think you do the XSLT transformation on the server and sending
the results as HTML back to the client (how you can do that without CSS,
even inline CSS, like the style attribute, is beyond me), right? Well,
in that case only the result counts (result of HTML).

You wrote:
<body onload="if (document.myBtn.disabled)
document.myBtn.disabled=false;" />

This will always make your button disabled, at least when there's an
element with ID/Name "myBtn". If there isn't, it should raise an error.
If it does not raise an error, you either have your browser off on
errors, or you have a global error handler somewhere in your scripts (or
in Cocoon).

You wrote:
<input name=myBtn onclick="this.disable=true;" />

This will do nothing, as the "disable" property of the 'this' object.
Use 'disabled' instead.

To me it sounds that you are mixing client side and server side. Client
side is, once it is generated, completely oblivious of what happens on
the serverside. It really doesn't matter a sip if your code is in the
parent xslt or in the xsl:include'd xslt. It only matter if the objects
you talk about are there or not and if you use the correct syntax. I
suggest you use document.getElementById('btnId') to get the button you
want, instead of the IE-only syntax in your example. Of course, the
ID-attribute must be unique.

Another solution often used where a form is submitted and sends the same
page again as a result, is the following.  The value can be set by
taking the name of the button used to perform the submit (it is send in
the http request with all the other fields), if there is no button name,
there is no form request.
<input type="hidden" name="result-from" value="btnX" />

Then, you can use the following on the button itself:
<input name=myBtn onclick="this.disabled=true;" />

One thing ponders me in the whole story. If you managed previously to
set the button to disabled using javascript on the onclick handler, it
must have been re-enabled after the refresh. And if you do not have a
refresh, how do you do that without using Ajax or related advanced
technology?

If I'm off-topic or misinterpreted your question, please provide enough
details and give a clear example what does work and what does not,
possibly including the offending xslt (though I doubt if that's the
issue here).

Cheers,

Abel Braaksma
http://www.nuntia.com

Current Thread
Re: Preventing second click, (continued) Oleg Konovalov - 28 Sep 2006 12:12:43 -0000 Abel Braaksma - 28 Sep 2006 18:11:22 -0000 Oleg Konovalov - 28 Sep 2006 21:21:35 -0000 Abel Braaksma - 28 Sep 2006 22:58:21 -0000 Oleg Konovalov - 29 Sep 2006 01:28:28 -0000 <= Abel Braaksma - 29 Sep 2006 07:10:05 -0000 Trish - 28 Sep 2006 12:03:51 -0000

<- Previous	Index	Next ->
Re: Preventing second click, Abel Braaksma	Thread	Re: Preventing second click, Abel Braaksma
Re: Opera's JavaScript API fo, M. David Peterson	Date	Re: XPath for matching multip, Dimitre Novatchev
	Month

PURCHASE STYLUS STUDIO ONLINE TODAY!

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

Cast Your Vote

We need your help – Vote for DataDirect XML Products!

Best SOA or XML site

Winners and finalists announced at SOA World Conference in November.

Download The World's Best XML IDE!

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

Subscribe in XML format

RSS 2.0
Atom 0.3


	Stylus Studio® Developer Network \| Contact Us \| Email this page