<div>To me, '</' or '/>' mean the tag's done. Therefore, '<select />...</select>' (or anything similar) is just plain wrong -- that would be a select list with nothing in it, then some options that are hanging out somewhere on their own, then an unmatched closing select. This shouldn't validate, serializers shouldn't allow it, and deserializers should simply ignore the options and '</select>' (or maybe dump the options' text to the output and just ignore the '</select>').
</div>
<div> </div>
<div>Now this, '<img src="..." />' -- which is what I thought this discussion was about initially -- is perfectly valid; it's nothing more than a tag without content.</div>
<div><br> </div>
<div><span class="gmail_quote">On 11/29/06, <b class="gmail_sendername">Stewart Brodie</b> <<a href="mailto:stewart.brodie@antplc.com">stewart.brodie@antplc.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">"Robert Sayre" <<a href="mailto:sayrer@gmail.com">sayrer@gmail.com</a>> wrote:<br><br>> On 11/29/06, Lachlan Hunt <
<a href="mailto:lachlan.hunt@lachy.id.au">lachlan.hunt@lachy.id.au</a>> wrote:<br>> ><br>> > I do not think it's a good idea to make the trailing slash conforming.<br>> > Although it is harmless, it provides no additional benefit at all and it
<br>> > creates the false impression that the syntax actually does something.<br>><br>> It does do something, in systems that think they are using XML<br>> (whether they actually are is another matter). It's possible it will
<br>> prevent many information-free validation errors, and give the HTML5<br>> more credibility as a result. Warning people about <img /> in the<br>> validator is a waste of their time.<br>><br>> > It's not a
<br>> > good idea to confuse them any more by giving the impression that it<br>> > works for some elements but not others. It's better to just say it<br>> > doesn't work at all and forbid it in all cases.
<br>> ><br>><br>> Better? This is an opinion, and it's not backed up by data. So far, it<br>> looks like Sam has the data on his side. People do it, and it tends to<br>> work interoperably.<br><br>Except when it doesn't.
<br><br>For example, here's a fragment of <a href="http://hotmail.com">hotmail.com</a>'s signup page, served as<br>"text/html". It's the only example I've come across to date:<br><br><br><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML
1.0<br>Strict//EN" "<a href="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd</a>"><br><html xmlns="<a href="http://www.w3.org/1999/xhtml">http://www.w3.org/1999/xhtml
</a>" dir="ltr"><br>...<br><select id="iRegion" name="pff00000000010004" /><br><script>...</script><br></select><br>...<br><br><br>The script just document.write
's loads of option tags (it's the country<br>menu). It's hard to know what the author thought was going on. Did they<br>think it was XHTML and just got stymied by the server configuration?<br><br>I'm still in favour of permitting the trailing slash, personally.
<br><br><br>--<br>Stewart Brodie<br>Software Engineer<br>ANT Software Limited<br></blockquote></div><br>