Maybe that's not what it's meant to do but I was expecting when a row
is selected the next time it is clicked it would be deselected. I was
thinking maybe that's just not how it works, but the rowUnfocus event
*is* fired... and the rowFocus is fired right after. I don't know if
this is a bug or if it is intentional or is a limitation or what.
Holding Ctrl while clicking allows one to deselect it, but that
doesn't seem as intuitive as select/deselect by just clicking the row.

Here's a quick/basic example/setup as reference:

http://jsfiddle.net/versatil/ZMLQP/

Reply via email to