-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Web - New text input does not work with autofill #4597
Comments
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open
|
Triggered auto assignment to @Jag96 ( |
It looks like #3414 is the offending PR here, the main change here was replacing I confirmed the issue happens on version 1.0.83-2 which is the version after this PR was merged (it isn't happening on 1.0.83-1 which is production atm). @kakajann can you please take a look? cc @roryabraham |
I'll be shortening the copy on the The regression here is that the input label overlaps with the value when the field gets auto-filled. |
@kavimuru, thanks for making this issue. I've changed the title and the description to reflect the exact problem that we need to get fixed. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
@parasharrajat, to clarify, the tab behavior has indeed been fixed by your PR. It's the auto-fill problem that we're still seeing. |
OK, I think I found the main issue for autofill. the technique to trigger the label position is not correct as it is not checking the current state of the input value. So instead of checking the prop value, we should check the value in the inputField. This value is a prop that will never update when the value is auto-filled.
We have to track the value changes using the |
It's good to revert the title to |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
OK, @parasharrajat, we're gonna make this issue exclusively about the auto-fill problem, and then Export this to Upwork, and get you hired for this auto-fill fix ASAP. Sound good? |
Yup @Luke9389 Fix is ready. |
Awesome, @MitchExpensify is getting the job set up in Upwork as we speak. |
I found this via upwork. The reason your autofill field isn't working is that autofill does not trigger the change event. I've encountered this before but I had to stray deep into my memory palace to figure out why. I'm hesitant to dedicate my time to this when someone could come along and swipe my investment but I thought I'd at least leave this comment to assist you. |
Thanks, @isagoico! The other two issues still occurring is expected. One of them was merged after you tested this, and the other hasn't been merged yet. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Paid! cc @parasharrajat |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
Expected Result:
When using auto-fill, the label should not overlap the value in the text box.
Actual Result:
When the text input is auto-filled, the label overlaps with the value.
Workaround:
Don't use autofill (unacceptable)
Platform:
Version Number:
1.0.85-0
Logs: https://stackoverflow.com/c/expensify/questions/4856
**Notes/Photos/Videos:
Expensify/Expensify Issue URL:
View all open jobs on Upwork
The text was updated successfully, but these errors were encountered: