RE: addEventListener to radio button

Yeah, the reason for disabling is so that people don't press submit twice.
There are a couple of options here: we could make it NOT disble in the case
of radiobuttons, OR, we could do the readonly thing if that would work
better.

Ideas?

Christian
----------------------------------------------
Christian Cryder [[email protected]]
Internet Architect, ATMReports.com
Barracuda - http://barracudamvc.org
----------------------------------------------
"Coffee? I could quit anytime, just not today"

> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]]On Behalf Of Shawn Wilson
> Sent: Monday, March 31, 2003 6:31 PM
> To: [email protected]
> Subject: Re: [Barracuda] addEventListener to radio button
>
>
> Hey Jake,
>
> What is the reasoning for disabling the element (other than submit
> buttons that may accidently get clicked more than once) anyways? Would
> setting readonly instead still produce the desired behavior?
>
> -shawn
>
> Jacob Kjome wrote:
> >
> > You know what, that won't work (at least not reliably) on radio
> > buttons.  Here's the problem...
> >
> > Setting disabled=true makes it so that the browser won't send the data
> > for that form element (at least in recent browsers such as Mozilla).
> > Setting this.disabled=true on buttons works because they don't contain
> > data needed for processing on the server.  However, when you do
> this for
> > elements that, themselves, contain data that are needed to be processed
> > on the server, you shoot yourself in the foot because the data never
> > gets sent for that disabled form element.
> >
> > The only thing that is curious is that you even get data at all
> for this
> > form element because it shoudn't be sent at all.  What browser are you
> > using?
> >
> > This means that we need to come up with another way selectively
> > disabling form elements so that we don't disabled elements that
> actually
> > contain data to send to the server.
> >
> > Jake
> >
> > At 11:11 AM 3/31/2003 -0500, you wrote:
> >
> >>Here is the generated
> >>code for the radio button
> >>input:
> >>
> >>
> >>
> >>
> >>
> >><input checked="checked" id="SpaceByRoadway"
> >>name="SpaceBy" onclick="this.disabled=true;
> >>document.EditForm.action='ActionEvent.event?$eid=TSSDownloadScre
> en$GetTSSDownloadHandler';document.EditForm.submit();
> >>return false;" type="radio"
> >>value="roadway">Roadway
> >>&nbsp;
> >>
> >>
> >><input id="SpaceByCorridor" name="SpaceBy"
> >>onclick="this.disabled=true;
> >>document.EditForm.action='ActionEvent.event?$eid=TSSDownloadScre
> en$GetTSSDownloadHandler';document.EditForm.submit();
> >>return false;" type="radio"
> >>value="corridor">Corridor
> >>&nbsp;
> >>
> >>
> >><input id="SpaceByStation" name="SpaceBy"
> >>onclick="this.disabled=true;
> >>document.EditForm.action='ActionEvent.event?$eid=TSSDownloadScre
> en$GetTSSDownloadHandler';document.EditForm.submit();
> >>return false;" type="radio"
> >>value="station">Station
> >>
> >>
> >>
> >>
> >>Im not sure exactly which version of barracuda Im using, but
> >>the timestamp on the class files in the JAR is
> >>2/21/2003.
> >>
> >>
> >>
> >>
> >> David R Robison
> >>
> >> Open Roads Consulting, Inc.
> >>
> >> http://www.openroadsconsulting.com
> >>
> >>
> >>
> >> -----Original Message-----
> >> *From:* [email protected]
> >> [mailto:[email protected]] *On Behalf Of *Jacob Kjome
> >> *Sent:* Friday, March 28, 2003 4:24 PM
> >> *To:* [email protected]
> >> *Subject:* Re: [Barracuda] addEventListener to radio button
> >>
> >>
> >>
> >>
> >> Hi David,
> >>
> >> I think this is a problem with the way Barracuda currently does form
> >> submittal via javascript.  Just like you said, the form gets submitted
> >> before the value is changed.  Normally you wouldn't run into this
> >> because you'd set you form components to their appropriate values and
> >> then click a "submit" button which would have the listener attached to
> >> it.  Hmm....
> >>
> >> Can you send a snippet of the generated html for this page just for
> >> reference?  Then we can think about what might be done to solve this
> >> issue.
> >>
> >> Oh, and what version of Barracuda are you using?  A release or the
> >> latest CVS?
> >>
> >> Jake
> >>
> >> At 03:54 PM 3/28/2003 -0500, you wrote:
> >>
> >> I have 3 <INPUT> elements all of type "radio" and with the same
> >> "name". I want
> >> to catch an event whenever a new selection is made. The values of the
> >> input
> >> fields are "one", "two", "three". I start with the <INPUT> "one"
> >> selected. When
> >> I click on "two" or "three" the event gets directed to my event
> >> listener but the
> >> value of the "radio" is still "one". No matter what I click, the value
> >> is always
> >> returned as "one". It seems that the event is firing when a radio
> >> button is
> >> clicked but before the selected value has been changed. Any ideas on
> >> what may be
> >> happening or how to work around it?
> >>
> >> Thanks,
> >> David Robison
> >> _______________________________________________
> >> Barracuda mailing list
> >> [email protected]
> >> http://barracudamvc.org/lists/listinfo/barracuda
>
> _______________________________________________
> Barracuda mailing list
> [email protected]
> http://barracudamvc.org/lists/listinfo/barracuda