No More Posting New Topics!

If you have a question or an issue, please start a thread in our Github Discussions Forum.
This forum is closed for new threads/ topics.

Navigation

    Quasar Framework

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search

    q-select using the keyboard instead of mouse clicks?

    Help
    4
    4
    1334
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • D
      daveline last edited by

      Curious if there is a way for users to navigate the q-select component using just the keyboard instead of mouse clicks? My users need to enter data very quickly and therefore are very keyboard centric. For example, they will tab between the various fields on a form and when they reach the “State” select box will type “f” for Florida or “aaa” for Arizona, then tab to the next field without ever using a mouse. The q-select is very nice and fancy, but I haven’t found a way to mimic the traditional keyboard usage of the html select.

      Any ideas?

      1 Reply Last reply Reply Quote 1
      • ssuess
        ssuess last edited by

        +1 for this!

        1 Reply Last reply Reply Quote 0
        • E
          eswann last edited by

          Agree 100%. In order to be accessible, we need to support “autoopen” for the q-select or at least some kind of “typeahead” to autoselect items when the user types. I don’t see an easy way to enable this. In addition, when I search using the filter, there is no way to arrow down to the actual options. These would be fantastic features.

          1 Reply Last reply Reply Quote 1
          • Hawkeye64
            Hawkeye64 last edited by

            Bumping. This is still needed. I’ve tried capturing @keyup.downArrow (setting Vue.config.keyCodes) and it doesn’t work. Event @keyup.enter (no defined keycodes) didn’t work to call my function. Seems the event is eaten up somewhere.

            1 Reply Last reply Reply Quote 0
            • First post
              Last post