There's more of a problem with cats in my area. I suppose the same applies!!!

>IMHO, an option group in some cases is more clear and natural than a checkbox. For example, "Do you want to kill the dog?" with the choices "yes" and "no". What's the prompt for checkbox? "Kill dog?" ... if checked, yes?
>
>I guess I'm thinking grammatically. A checkbox to me represents a boolean flag, an indirect question, while putting a yes/no checkbox denotes direct action and the natural control for a firect question. The difference being (former to latter) .. "oh, btw, I want to kill the dog" as opposed to "Yes! Kill the dog!"
>
>>>When someone wants to do something that violates UI standards, I generally don't answer with code (lol). But in this case, I can think of plenty of situation where a Yes/No is controlled by an OptionGroup or the functional equivalent thereof.
>>
>>I quoted one scenario where I think it's ok. But in most situations, IMO, its just plain goofy.
>>
>>> I'd really like to see a quote.
>>
>>Ok, since I'm too lazy to dig through the UI standards, I'll concede to say only that a checkbox is designed to handle boolean values, and optiongroups are designed to handle cases where two or more choices each need their own explanation.
>>
>>If you use an optiongroup for a simple boolean value, then what is a legitimate use for a checkbox?