-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Fix: cursor on Login button becomes cursor: not-allowed
in pristine state
#2452
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
Conversation
🎉 Thanks for opening this pull request! Please check out our contributing guidelines if you haven't already. |
cursor: not allowed
cursor: not allowed
cursor: not-allowed
in pristine state
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good but let's clean up the import
line before merging.
@@ -1,4 +1,4 @@ | |||
import React from 'react'; | |||
import React, { useEffect, useState } from 'react'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
import React, { useEffect, useState } from 'react'; | |
import React from 'react'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done !
Remove `pristine` import
@lindapaiste, could you please take a look? I've removed unnecessary imports. The only thing I believe needs attention is the 'value' prop storing the user's input. Do you think it's safe to leave it this way, or should I make changes here if necessary? |
I don’t think that the value prop is a problem? You can definitely research what the best practices are for dealing with an input type=“password”, but let’s tackle that in a separate PR. If it’s easy, can you roll back the changes in the package-lock.json file and in the Button file? It’s it’s a pain then no worries. |
@lindapaiste, not a problem at all. I've rolled them back. My apologies for missing that. |
We’re just about ready to merge but it’s failing lint checks due to a formatting issue. We use a package called Prettier so that all code is formatted nicely and consistently. Now that you removed one of the destructured properties, Prettier thinks that it should all be on one line instead of on separate lines. If you run the |
@lindapaiste The test passed! Thanks for the suggestion |
Fixes #2228
Upon some investigation, I found that the
value
prop of the input field in a web form is not able to recognize Google Autocomplete with a password manager. Seems like it is bypassing Reacts state management.screen-capture.webm
Changes:
I have verified that this pull request:
npm run lint
)npm run test
)develop
branch.Fixes #123