Boolean attributes in HTML are normally used to indicate things like whether a checkbox is checked or whether an option is selected or whether an input is disabled.
I have seen several implementations of HTML boolean attributes over the years. Initially you just added the relevant word to the element to symbolise that it was checked, selected or disabled.
<input type="text" name="example" disabled>
When XHTML came along, the strict requirement for all attributes to have a value resulted in the rather bizarre practice of putting the attribute name in quotes after the attribute.
<input type="text" name="example" disabled="disabled">
Why on Earth this couldn’t be disabled=”true”, I’ll never know. In fact, some people started to say that using true and false values was the “HTML 4″ method and using weird repetitive words was the “XHTML” way. This is actually incorrect as the HTML 4 specification actually says that you should use either the same method as XHTML or the minimised form.
<input type="text" name="exampleA" disabled="disabled"> <input type="text" name="exampleB" disabled>
This rule remains in HTML 5, where the following variations are allowed…
<input type="text" name="example1" disabled="disabled"> <input type="text" name="example2" disabled=disabled> <input type="text" name="example3" disabled="DISABLED"> <input type="text" name="example4" disabled=""> <input type="text" name="example5" disabled>
“If the attribute is present, its value must either be the empty string or a value that is a case-insensitive match for the attribute’s canonical name, with no leading or trailing white-space.”
Personally, I think we should all stick to the simple minimised form (example5). It works in all browsers, it doesn’t pretend to be XHTML and it doesn’t imply that the value of the attribute is useful. If the value of the attribute was true / false, it would make sense – but it isn’t and it doesn’t.