Yes, in some cases, we need to provide specific tabindex values due to the nature and complexity of some of the forms in our app. Great, thank you so much!

@azeredobr I’m not doing this with quasar yet. I have it done on another project and I was hopping that quasar would bring this by default, so I wouldn’t need to re implement it by myself again.

I think the best way to this would be two complete separated but, of course related implementations:

A new boolean prop, like “selected_checkbox”, true by default that keeps the current checkbox for selecting rows, but when false, the visual state of selected of a row would be an css effect of a “pressed” row and no checkbox would appear; Keyboard support for space, up and down arrows being select/unselect, row up and row down respectively. Naturally, a table now would receive focus (and have a @focus listener) via tab navigation or click, witch would initiate the keyboard support.

Thanks