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

[BUG]: whileTap should have priority over whileFocus #1221

Closed
smeijer opened this issue Jul 16, 2021 · 1 comment · Fixed by #1328
Closed

[BUG]: whileTap should have priority over whileFocus #1221

smeijer opened this issue Jul 16, 2021 · 1 comment · Fixed by #1328
Labels
bug Something isn't working

Comments

@smeijer
Copy link

smeijer commented Jul 16, 2021

Describe the bug

I believe that whileTap should have priority over whileFocus

IMPORTANT: Provide a CodeSandbox reproduction of the bug

A CodeSandbox minimal reproduction will allow us to quickly follow the reproduction steps. Without one, this bug report won't be accepted.

https://codesandbox.io/s/framer-motion-focus-zz81e?file=/src/App.js

Steps to reproduce

Steps to reproduce the behavior:

  1. Open the sandbox
  2. Click on a few times on both buttons
  3. The one that uses whileFocus, never shows the > on the whileTap position

Expected behavior
As I need to focus an element, before I'm able to "tap" it, I believe that Tap transforms should take priority over focus transforms.

Video or screenshots

framer-motion.mp4

Environment details

browser:   Chrome 91.0.4472.77
os:        Linux, Ubuntu 20.04
@gilsonnunesfilho
Copy link

Any updates on this? Seems that whileFocus still blocks whileTap on my projects.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants