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

    Select (q-select) @new-value not triggering on mobile

    Framework
    2
    2
    126
    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.
    • J
      jainsuneet last edited by jainsuneet

      I am developing a cordova mobile application and I am stuck with the q-select not triggering @new-value event on the mobile app. Documentation states that it listens for key enter event but on mobile I am not sure how it will trigger. I have a form with q-select and other inputs. What I want is that when someone enters new value in q-select and go to next input the @new-value should trigger but this is not happening. Maybe someone from the community can help me.

      <template>
        <div class="q-pa-md">
          <q-select
            filled
            v-model="model"
            use-input
            use-chips
            multiple
            input-debounce="0"
            @new-value="createValue"
            :options="filterOptions"
            @filter="filterFn"
            style="width: 250px"
          />
        </div>
      </template>
      
      dobbel 1 Reply Last reply Reply Quote 0
      • dobbel
        dobbel @jainsuneet last edited by

        @jainsuneet

        Does your code work as expected in the browser in SPA mode?

        Documentation states that it listens for key enter event but on mobile I am not sure how it will trigger.

        I don’t read that explicitly in the q-select documentation for @new-value …

        What I want is that when someone enters new value in q-select and go to next input the @new-value should trigger but this is not happening.

        Is this really what you want? Because I interpreted this as follows:
        If the 'next' input component gets focus, check if the the q-select has a new value and then do_something/fire an event.

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