You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 13, 2018. It is now read-only.
I have a Paper FAB button in my app. I'm experiencing an issue on mobile devices with the current Chrome 40: When I tap on such a button the focussed state is being rendered (elevation on the z-axis).
It can also be reproduced when the mobile emulation mode of desktop Chrome is turned on and the emulation featre "Emulate touch screen" is enabled.
By tracking the issue down, it seems like it has its origin in core-focusable. By inserting some console.logs I found that on a tap the following functions are called in this order: _downAction, _upAction and then _focusAction.
Shouldn't _focusAction be called between _downAction and _upAction (if at all)? That way the focus state wouldn't be rendered, because this is prevented when this.pressed is set to true.