Re: Voting Issues with Lynx (and other browsers)

in reply to Voting Issues with Lynx (and other browsers)

According to the HTML 4.01 Specification:

If no radio button in a set sharing the same control name is initially "on", user agent behavior for choosing which control is initially "on" is undefined.
...
Since user agent behavior differs, authors should ensure that in each set of radio buttons that one is initially "on".

As to the button clearing all choices, as far as I know it would require using javascript, which is not supported by lynx.

Cheers

Antonio
__
The stupider the astronaut, the easier it is to win the trip to Vega - A. Tucket

Comment on Re: Voting Issues with Lynx (and other browsers)

Replies are listed 'Best First'.
Re: Re: Voting Issues with Lynx (and other browsers) by rjimlad (Acolyte) on Sep 29, 2002 at 14:13 UTC
You're absolutely right. In fact, what ideally should be used is not checkboxes but <select> elements eg: `<select name='vote_XXXXX'> <option value='' selected='selected'></option> <option value='1'>++</option> <option value='-1'>--</option> </select></option>` [download] ...which would have the minor extra quirk that the resultant form argument would be passed to the script even if nothing had been selected, but it would get the job done. And lynx is absolutely fine with handling <select>s. Note: In the above example, I've used "" rather than '0', as "" (the empty string) can usually be considered to be (effectively) undefined, in the context of HTTP form contents.	[reply] [d/l]

Replies are listed 'Best First'.

Re: Re: Voting Issues with Lynx (and other browsers)
by rjimlad (Acolyte) on Sep 29, 2002 at 14:13 UTC

You're absolutely right. In fact, what ideally should be used is not checkboxes but <select> elements eg:

<select name='vote_XXXXX'>
   <option value='' selected='selected'></option>
   <option value='1'>++</option>
   <option value='-1'>--</option>
</select></option>
[download]

...which would have the minor extra quirk that the resultant form argument would be passed to the script even if nothing had been selected, but it would get the job done. And lynx is absolutely fine with handling <select>s.

Note: In the above example, I've used "" rather than '0', as "" (the empty string) can usually be considered to be (effectively) undefined, in the context of HTTP form contents.

[reply]
[d/l]

In Section Perl Monks Discussion