Jeff,
Thanks for your reply.
Do you know where I can find doc describing the "checked" attribute ?
Or better yet some examples of this type of form input manipulation.
This seems to be a rather undocumented/confusing way to handle a very
simple concept. Then again I'm probably not looking at the right
documentation. The sample I found in the mailing list archive threw
me as it uses value and undef to turn the input "off". I guess
I missinterpreted "off" as meaning unchecked.
An example of evaluating a checkbox's text value then testing if it's
"checked", then checking it (turning it ON) if it isn't, would be extremely
helpful. Maybe I can provide one if I ever get this foolish thing to work.
Thanks,
Steve
> The value can be defined with the box not being checked; it's two separate
> properties. So making the value undef won't uncheck the box, it will just
> make a useless checkbox in the sense that even if it's checked nothing
> gets sent to the server. If it's checked then the value gets sent to the
> server.
>
> Have you tried it using the checked attribute instead of value?
>
> -- Jeff
>
pop-server.stny.rr.com