> ------- Additional Comments From [EMAIL PROTECTED] 2003-10-31 15:27 ------- > You should never be rendering only a single radio button because it's a huge > usability issue. The user can never uncheck a single radio button once they've > checked it. In this case, you should probably be using a different form control > like a select box.
These are excellent points, and the question becomes is this boundary condition a useability "should" or a technical "must". HTML spec is no help, I looked. It talks about sets, but doesn't define set as two or more. I'm having horrible visions of someone doing a query driven voting application using radio boxes... Those aside, IMHO think the utility of having the trivial case handled in the framework is more useful than having application logic check for it, and is generally worth a useability tradeoff. Ernie Argetsinger --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
