Re: lynx-dev checkbox with empty value

[mattack]

On Tue, 2 May 2000, Klaus Weide wrote:

>Date: Tue, 2 May 2000 17:18:14 -0500 (CDT)
>From: Klaus Weide <address@hidden>
>Reply-To: address@hidden
>To: address@hidden
>Subject: Re: lynx-dev checkbox with empty value
>
>On Tue, 2 May 2000 address@hidden wrote:
>> On Tue, 2 May 2000, Klaus Weide wrote:
>> >Neither could I; so value="" should be treated as any
>> >other value.
>> 
>> empty meaning OFF makes far more sense than empty meaning ON.  The default
>> state is off, until you turn it on.
>
>We're not talking about *whether* something gets sent to the server
>for a checkbox.  That depends on whether it is in state "on" or "off",
>which is toggled by the user.
>
>We're only talking about *what* gets sent *if* something gets sent.
>The similarity between the string "on" that may be sent to the server
>and the notation "on" for one state of the toggle is purely coincidental.

so the issue isn't the state that the checkbox *starts out* in? [turned on or
off]?  That's what it seemed like from the original message.