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!

Okay, thanks! I am on 0.14.4 and trying it with QInput: <q-input name=“email” type=“email” float-label=“Email” v-model=“email” tabindex=“3”/>

However, tabindex does not get rendered, nor (obviously) work during tabbing.

I checked the v0.14 branch and do not see tabindex:
https://github.com/quasarframework/quasar/blob/v0.14/src/components/input/QInput.vue

I may likely be missing something.

Thanks!

Thanks. That works. I am specifically talking about the Quasar components not having this support, though.

We have some pretty elaborate forms in our application, which require the use of the tabindex attribute to help with user navigation/workflow (desktop). I noticed when trying to set this attribute on Quasar components: it does not render. Could it be added? Or, better yet, add a way to pass custom attributes to input components?

While testing out Quasar, I noticed that some components, take the Select component for instance, do not have any built-in keyboard navigation support. For example: the Select component does not open the options list on ‘enter’. The option list cannot be navigated by arrows, nor selected by ‘enter’. Is this intentional? I can build the events myself, but wanted to check if this was done for a reason. And, if not, if this something that could be added to the roadmap? (if it hasn’t already… I looked and didn’t see it, but may have missed it) Thanks!