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

Latest update has broken our solution in Chrome #83

Closed
taeuscherpferd opened this issue Dec 7, 2021 · 5 comments
Closed

Latest update has broken our solution in Chrome #83

taeuscherpferd opened this issue Dec 7, 2021 · 5 comments

Comments

@taeuscherpferd
Copy link

taeuscherpferd commented Dec 7, 2021

After the latest update, after flipping a tile, the back of the tile is no longer interactable. This only happens in Chrome as far as I can tell. It also seems to have slowed down all of the other animations in our solution. We have downgraded the package to fix, and will probably stay on the downgraded version for the foreseeable future, but I just thought that you should be aware. 👍

@AaronCCWong
Copy link
Owner

Thanks for reporting this. Can you provide a minimally reproducible example?

@Sairav
Copy link

Sairav commented Dec 8, 2021

Same for me , I am using TextField as the second child (the element that shows up on flip) , it is not interactable.
On hover on the input field of the TextField , mouse pointer doesn't change to cursor, and it is not editable at all . I have also downgraded it.

@rafael-ferreira-11
Copy link

Same for me, downgraded to 1.1.3 which fixed the issued. My "Back card" is a form with several inputs and buttons

@sTsaturian
Copy link

sTsaturian commented Dec 8, 2021

Doesn't work for me either. Here is an example: https://codesandbox.io/s/basictextfields-material-demo-forked-7zf38?file=/demo.tsx

There are some other issues with the back side as well, such as not changing cursor to pointer when hovering over links. I noticed that the front card always had z-index:2, regardless of the flipped state. Maybe it's related.

@AaronCCWong
Copy link
Owner

Pushed v1.1.5 which reverts the change causing this issue. Please reopen if that does not fix the issue.

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

No branches or pull requests

5 participants