Care to explain that line of reasoning?Quote:
Originally Posted by Twey
I fail to see any problems with that (though the OP would undoubtely want to style it), and it facilitates precisely what the original post describes.HTML Code:<fieldset>
<legend>Platform</legend>
<ul>
<li>
<label for="linux">
<input id="linux" name="platform" type="radio" value="linux" checked>
Linux
</label>
</li>
<li>
<label for="windows">
<input id="windows" name="platform" type="radio" value="windows">
Windows
</label>
</li>
</ul>
</fieldset>
<fieldset>
<legend>Server Disposition</legend>
<ul>
<li>
<label for="shared">
<input id="shared" name="server-disposition" type="radio" value="shared" checked>
Shared
</label>
</li>
<li>
<label for="dedicated">
<input id="dedicated" name="server-disposition" type="radio" value="dedicated">
Dedicated
</label>
</li>
<li>
<label for="reseller">
<input id="reseller" name="server-disposition" type="radio" value="reseller">
Reseller
</label>
</li>
</ul>
</fieldset>
You really have no choice. Relying on client-side validation to do the all work is practically begging for someone to submit false or erroneous data to you. For example, simply having client-side scripting disabled means that the user is unencumbered from any constraint you would like to enforce. Not even a type of control (like radio buttons or select elements) can provide security in a situation like that.Quote:
Originally Posted by gastongr
Mike
