<p>I can accept that. It's just a shame that true and false can't be supported for something called a boolean attribute. </p>
<p>Anyone have any thoughts on setAttribute vs. setting the attribute directly? My test show that they both work. </p>
<p>Thanks,<br>
Brian</p>
<p><blockquote type="cite">On Dec 8, 2009 1:57 PM, "Tab Atkins Jr." <<a href="mailto:jackalmage@gmail.com">jackalmage@gmail.com</a>> wrote:<br><br><p><font color="#500050">On Tue, Dec 8, 2009 at 3:48 PM, Brian Kuhn <<a href="mailto:bnkuhn@gmail.com">bnkuhn@gmail.com</a>> wrote:
>> but it's invalid to set it ...</font></p>Indeed, async="true" does set it to be on. However, so does<br>
async="false", async="off", async="no", and any other string you can<br>
think of that might imply that it's turned off. Setting it to *any*<br>
value turns it on, so it's best to avoid values that would lead to<br>
confusing results. The two values that are currently valid are the<br>
minimum necessary, and neither have antonyms that would confuse<br>
people.<br>
<font color="#888888"><br>
~TJ<br>
</font></blockquote></p>