Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Buttons are getting stuck in the hovered state on iOS #77

Open
razcakappa opened this issue Dec 15, 2015 · 5 comments
Open

Buttons are getting stuck in the hovered state on iOS #77

razcakappa opened this issue Dec 15, 2015 · 5 comments

Comments

@razcakappa
Copy link

Button in the "Background Transitions" section are getting stuck in the hovered state unless you click in empty space:
I'm not sure this is a purposeful feature. However I'd like to know how to remove this?

@razcakappa
Copy link
Author

Update: This happens only on iPad and Touch devices.

@IanLunn
Copy link
Owner

IanLunn commented Dec 15, 2015

It is due to the element having focus when pressed. Pressing elsewhere causes it then to lose focus. Remove the :focus selector from each effect to workaround this.

@razcakappa
Copy link
Author

@IanLunn I've removed the both :active and :focus selector and tested on iPad. However the problem was there.

@IanLunn
Copy link
Owner

IanLunn commented Oct 21, 2016

This is expected browser behaviour although maybe we can work around it without the use of JavaScript.

@IanLunn IanLunn changed the title "Background Transitions" section buttons are getting stuck in the hovered state Buttons are getting stuck in the hovered state on iOS Mar 22, 2017
@IanLunn
Copy link
Owner

IanLunn commented Mar 22, 2017

Just to update on this. When you press a button on iOS it is considered as being hovered over. Pressing the button a second time applies hover again so the effect never actually stops. JavaScript would be required to work around this (probably use of the Pointer Events API, active classes, etc) which is outside of the project scope.

I may add this as an optional script in the future but for now, won't fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants