dojo.setSelectable should be dojo.attr('selectable')

[nonken]

In line with the Dojo api we should offer dojo.setSelectable as dojo.attr('selectable', ...) as well

[dante]

fwiw, dojo.attr doesn't handle stuff like this yet well I think.

dojo.attr(n, "checked", false) doesn't do what you think

you need to dojo.removeAttr(n, "checked") to de-check. attr(n, "selectable", Boolean) would likely suffer the same limitation unless special considerations were to take place.

@uhop / @jamestag - is this something we should consider shfiting around with aliases and deprecate set* in 2.0?

[Eugene Lazutkin]

We need to come up with the general strategy for Boolean properties (selected/checked/disabled/readonly/...). They all have numerous quirks developer should be aware of when setting their values --- the perfect thing for a convenience helper.

[Eugene Lazutkin]

One way to handle it is to make sure that:

dojo.attr(node, "checked", true);  // should select things
dojo.attr(node, "checked", false); // should deselect things
dojo.attr(node, "checked") instanceof Boolean // should be always true

The only complication implementing this from the top of my head is to make sure that in the radio group only one choice is selected --- it requires some non-trivial code with looping, and potentially document-wide querying.

[James Burke]

I prefer addressing this in a 2.0 timeframe, since attr does seem to be growing outside just plain attribute get/set into property and attribute get/set. Or at least, I think we have bitten off enough new features for a 1.3 release.

[dylan]

Given that no one has shown interest in creating a patch in the past 5+ years, I'm closing this as patchwelcome.