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

    0.15 @Click QItem not working

    Help
    6
    8
    5185
    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.
    • N
      Nicholas last edited by

      Hi,
      I’m having trouble making @click work on <q-item>.
      Worked fine on 0.14 but whenever I try to do @click="" on QItem in 0.15 it does nothing.

      Any workaround?

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

        @click.native=""

        N 1 Reply Last reply Reply Quote 1
        • N
          Nicholas @MagoSchmidt last edited by

          @magoschmidt Thanks for that! Any reason why we need to use .native rather than the normal @click?

          1 Reply Last reply Reply Quote 0
          • O
            ouaR last edited by

            I don’t understand why @click was removed from QItem, it’s a normal behavior for a list item to be clicked !

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

              @ouaR read this: https://github.com/quasarframework/quasar-framework.org/blob/dev/source/guide/quasar-upgrade-guide.md#some-components-need-native-modifier-for-events-now

              then you will understand!

              1 Reply Last reply Reply Quote 2
              • D
                Dabnis last edited by Dabnis

                Hi,
                My issue with these types of changes is that Quasar is becoming less & less Vue. When working a multiple Vue code bases this type of change is making it harder to maintain a common coding standard.
                While the link aboave states what we must now do it does not explain why!

                Unfortunately this has now put Quasar outside of the scope of approved development technologies for my company as the fear is it will become more & more diverse from Vue so we will be returning to ‘pure’ Vue.

                1 Reply Last reply Reply Quote 0
                • W
                  wannymiarelli last edited by wannymiarelli

                  @Dabnis well i think this is more about complexity. I dont really know the exact reason for removing the @click from the Q-Item but i presume there should be one.
                  Quitting a framework because it has some trade-off is not a smart idea, i dont know how to proceed

                  1 Reply Last reply Reply Quote 0
                  • D
                    Dabnis last edited by

                    Dropping Quasar is more than ’ because it has some trade off’, it’s a fear that the deviation from the Vue phylosphy & standards continue to esculate in the future & reaches a stage where it’s so fundamentally different from Vue is basics like @clickk events, but potentially many more.

                    We initially thought of Quasar as an extension to Vue, a GUI front end framework based on Vue. From a production point of view we thought that to use Quasar we would simply update & add to our existing Vue skillsets, but as fundemental deviations away from Vue fundementals grow within Quasar then the Vue based minimum skill-set advantage disapears. We don’t have the time to learn another adaptation of Vue, that’s based on Vue, but different.

                    Hope this explains our decision.

                    Dab’s

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