-
Notifications
You must be signed in to change notification settings - Fork 17
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
React 18 CardElement visibility hidden #186
Comments
same issue |
@douglasmiller any update on this? |
@laviniu-creatopy, @PabloSuarez, @ridersofrohan: I created this codesandbox with the demo code from the repository and everything appears to be working for me. Are y'all seeing a different behavior? If so, could one of y'all provide a codesandbox so that we can reproduce the issues that you're experiencing? |
Thinking this may be related to #182 and use of |
@douglasmiller it works on JS but fail with typescript, I can't create the sandbox now but I'll |
Actually, I was able to repro this issue in the sandbox. The issue occurs with a combination of using import React from "react";
import { createRoot/*, render*/ } from "react-dom";
// ...
function App() {
return (
<div>
<React.StrictMode>
{/* ... */}
</React.StrictMode>
</div>
);
}
// render(<App />, document.querySelector(".App"));
const root = createRoot(document.querySelector(".App"));
root.render(<App />); |
@PabloSuarez, I was able to reproduce your issue with the strict mode changes that @Smolations suggested in this codesandbox. The issue persists if Could you verify that the latest version of this package is working for you as well? |
Thanks to this excellent contrib from @WillXing. |
Describe the bug
When using react@18 the input for the card element stays with visibility: hidden, the date and CVV fields are working
To Reproduce
Use the library with react@18 and demo code from https://github.com/recurly/react-recurly/blob/main/demo/src/card-element-demo.js
Expected behavior
to let me type the card number :)
Your Environment
1.2.4
18.2.0
Google Chrome Version 104.0.5112.101
The text was updated successfully, but these errors were encountered: