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

    QSelect @change not working (codepen included) (solved)

    Framework
    1
    3
    2402
    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.
    • M
      mattabdi last edited by mattabdi

      I am trying to use @change with QSelect and it doesn’t seem like the event is being kicked off.

      codepen: https://codepen.io/mattabdi/pen/ZqrdoK

            <q-select
              v-model="selected"
              float-label="Issue Type"
              :options="options"
              @change="atChange"
              style="width: 80%;"
            >
            </q-select>
      
      new Vue({
        el: '#q-app',
        data: function () {
          return {
            version: Quasar.version,
            options: [
              {value: 'a',label:'a'},
              {value: 'b',label:'b'},
              {value: 'c',label:'c'}
            ],
            selected: '',
            changed: false
          }
        },
        methods: {
          notify: function () {
            this.$q.notify('Running on Quasar v' + this.$q.version)
          },
          atChange: function () {
            this.changed = true
          }
        }
      })
      
      1 Reply Last reply Reply Quote 0
      • M
        mattabdi last edited by

        Seems like a known issue but not documented in the docs
        https://forum.quasar-framework.org/topic/1867/solved-qselect-change-broken-in-0-15

        1 Reply Last reply Reply Quote 0
        • M
          mattabdi last edited by mattabdi

          I replaced @change with @input and that seems to have fixed the issue.

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