-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Chrome - animation glitch #593
Comments
This may happen if the up event does not occur. If you right click and open a browser dialog, that eats the mouseup, or if your finger leaves the screen without sending a touchend. I'm not sure how much of this we can fix, except to clean up missing events on the next down. |
It sounds like the up event didn't get fired. It shouldn't happen if you are just doing a click. So sounds like a bug somewhere. But I couldn't reproduce the problem using Chrome 35.0.1916.153 on http://www.polymer-project.org/components/paper-elements/demo.html. |
I can reproduce this problem repeatedly on my Chrome 35.0.1916.153 (32bit) running under Win 8.1 (including incognito mode - i.e. without any plugins) on http://www.polymer-project.org/components/paper-elements/demo.html. I installed Chrome Canary 38.0.2084.0 (64-bit) and tested it there - it works without any problems. Interestingly, I tried to reproduce this bug on http://www.polymer-project.org/apps/topeka/ and I couldn't; both Chrome versions work well with checkboxes and radioboxes that are there - no animation problems. |
I put some issues on the respective repos for checkbox and radio-button before noticing the issue mentioned here already. Have only been able to reproduce in Chrome. Works fine in IE11 Side note - should we post issue relating to components here or on the respective repos |
We prefer on the component repos so it's easier to organize On Mon, Aug 4, 2014 at 3:12 PM, wing5wong notifications@github.com wrote:
|
Duplicate of googlearchive/paper-ripple#16 |
Sometimes animations don't finish and get stuck.
Example:
The text was updated successfully, but these errors were encountered: