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

    [Solved] Strange Behavior - Going past last q-btn in q-toolbar activates the first q-btn.

    Framework
    3
    6
    160
    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.
    • Q-Brad
      Q-Brad last edited by Q-Brad

      Hi all,

      New here to the forum. I’ve been using Quasar for a while now - but when I started using the newer version 1.9.8, I seem to be having an issue with the q-toolbar/q-btn. Has anyone been experiencing this?

      Image-1: Hovering over the last button normally.
      ButtonOverrun 44.png

      Image-2: Moving past the last button highlights the first button and if I click, will activate the first button.
      ButtonOverrun 50.png

      I’ve only made a few changes to the code after creating the project… as such:

      <q-header>
      	<q-toolbar>
      		<q-toolbar-title>App Title</q-toolbar-title>
      		<q-btn flat dense round aria-label="Comments" icon="r_comment_text" to="/comments" />
      		<q-btn flat dense round aria-label="Notifications" icon="r_notifications" to="/notify" />
      		<q-btn flat dense round aria-label="Account" icon="r_account_circle" to="/account" />
      	</q-toolbar>
      </q-header>
      

      Anyone else getting this?

      metalsadman 1 Reply Last reply Reply Quote 1
      • J
        jraez last edited by

        As you use to I guess you have a vue-router. Then check your routes definitions and see what is matching when you change route.

        1 Reply Last reply Reply Quote 1
        • metalsadman
          metalsadman @Q-Brad last edited by metalsadman

          @Q-Brad can make a codepen pls. thx.

          edit. ok just tested, and looks like the culprit is a bad icon name, comment_text seem wrong. see https://codepen.io/metalsadman/pen/abOEmVL

          yep it’s wrong https://material.io/resources/icons/?icon=comment&style=round should just be r_comment.

          Q-Brad 1 Reply Last reply Reply Quote 2
          • Q-Brad
            Q-Brad @metalsadman last edited by Q-Brad

            @metalsadman Thanks so much! That solved my issue. It was driving me nuts a little bit. The strange thing is that, as you can see from my images, the icon was still displaying properly. Weird.

            Edit: Is there a way to mark your answer as the correct one… or solved?

            metalsadman 1 Reply Last reply Reply Quote 1
            • metalsadman
              metalsadman @Q-Brad last edited by

              @Q-Brad np, you can just put a prefix in your post title, usually peeps just put [Solved] topic... something.

              1 Reply Last reply Reply Quote 1
              • Q-Brad
                Q-Brad last edited by

                Thanks… done.

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