Btn not returning to original state on touch platforms

[spectrolite]

Software version

Quasar: 0.14-beta
OS: Android 6.0.1
Browsers: Chrome 59 and beta

What did you get as the error?

Most buttons get stuck in the hover state at the end of the ripple (instead of going back to normal). Clicking anything else restores the correct style. Buttons that trigger a modal or give focus to some other element are not affected. But most simple buttons and possibly some configurations of fab or other quasar component containing a button may be affected.

What were you expecting?

The button returns to its original state after the ripple ends.

What steps did you take, to get the error?

Touch a simple button (which has a dark background color, otherwise it's barely noticeable)
e.g.

<q-btn color="deep-purple-9" icon="gps_fixed">
  Test
</q-btn>
<q-btn color="deep-purple-9" icon="gps_fixed">
  Reference
</q-btn>

[rstoenescu]

Hmm, could not reproduce in my tests. Will investigate. Thx for reporting.

[spectrolite]

It also happens to the slider button, and basically any button that is not followed by a change in focus.

[aldanor]

Happens to me as well, in both mat and ios themes.

In my example it's something like this:

<q-btn big flat icon="done" color="positive" />

After tappping the button (iPhone, iOS 10), the button doesn't return to original state.

[rstoenescu]

Hi, any gif available to highlight the issue pls?

[aldanor]

Looks like it also happens in the official examples in the docs -- the easiest way to see it is tapping the "outline" buttons.

[aldanor]

I'm not sure how to record a gif since it's a phone and not an emulator :) Basically, after tap the button is stuck in hover state. You then have to tap elsewhere in the body to reset it back.

[aldanor]

For the sake of completeness, I think this also happens to clickable QListItem on mobile. (gets stuck in hover until you tap on something else)

[aldanor]

(ios emulator)

[rstoenescu]

Thanks for the additional information. Fix available in edge and future v0.14.2.

[aldanor]

@rstoenescu Thanks! Wonder if this could also be fixed for QListItem? (it's the same kind of problem)