Heath, I've been think about this problem and I decided to do a simple test. I created a foo bean with a boolean property. I set its initial value to be true and gave the bean session scope. On my JSF page I created a <h:selectOneCheckbox> that was bound to this foo bean. I also added a value change listener attribute which pointed to a method on foo bean that logged any changes.
If I changed the value of the checkbox and submit, the change listener detects the change (as expected.) If I change the page so that the checkbox is disabled and repeat the experiment, the change listener does not fire (the desired behavior.) It would seem this works just as expected. I haven't figured out where in the code this is being handled but I bet the decoding is being skipped if the component is disabled. If so, I can't see why you would have a problem on your end. It doesn't seem like a javascript workaround (or a hidden input) would be necessary. sean On Wed, 12 Jan 2005 15:59:54 -0600, Heath Borders <[EMAIL PROTECTED]> wrote: > According to the W3C spec, disabled inputs don't submit their value > with the form. > > I guess this means that we shouldn't go out of our way to work around > this problem because its not a problem at all! :) > > http://www.w3.org/TR/html4/interact/forms.html#disabled > > On Wed, 12 Jan 2005 15:49:31 -0600, Heath Borders > <[EMAIL PROTECTED]> wrote: > > Yeah, that might not be a bad idea. > > > > On Wed, 12 Jan 2005 16:41:00 -0500, Sean Schofield > > <[EMAIL PROTECTED]> wrote: > > > > I was just talking about my group's solution. For reasons you stated, > > > > we can't have it as the general solution. > > > > > > Should we open a bug on this then? It would seem the problem remains > > > unresolved ... > > > > > > > -Heath Borders-Wing > > > > > > > -- > > -Heath Borders-Wing > > [EMAIL PROTECTED] > > > > -- > -Heath Borders-Wing > [EMAIL PROTECTED] >
