My point was that regardless of the validity of the code, it is sometimes invalid communications/user interface to have one and only one 'checked' item at all times. I said, and still hold to the view, that sometimes a form has to be presented with none of the radio buttons 'checked'.
That's the relevance to standards - i.e. that if it's only standard if there is a default radio button and never valid if none of them are 'checked' then the standard is wrong and ought to be changed.
Cheers
Mike Kear
Windsor, NSW, Australia
Certified Advanced ColdFusion Developer
AFP Webworks
http://afpwebworks.com
ColdFusion, PHP, ASP, ASP.NET hosting from AUD$15/month
--------- Original Message --------
From: wsg@webstandardsgroup.org
To: "WSG" <wsg@webstandardsgroup.org>
Subject: Re: [WSG] Default state of radio buttons. (Maybe OT?)
Date: 02/02/05 03:56
I hesitantly suggest a good place for this discussion would be on Justin
French's Interface list.
http://lists.indent.com.au/mailman/listinfo/interface
Cheers
Chris Blown
________________________________________________
Message sent using UebiMiau 2.7.2
****************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ******************************************************
