fix: 31415 Input field on Login page gets white background after using auto-fill#32332
Merged
neil-marcellini merged 4 commits intoExpensify:mainfrom Dec 5, 2023
Merged
fix: 31415 Input field on Login page gets white background after using auto-fill#32332neil-marcellini merged 4 commits intoExpensify:mainfrom
neil-marcellini merged 4 commits intoExpensify:mainfrom
Conversation
melvin-bot
bot
requested review from
parasharrajat
and removed request for
a team
|
@parasharrajat Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button] |
parasharrajat
suggested changes
Dec 1, 2023
| } | ||
|
|
||
| /* Customizes the background and text colors for autofill inputs in Chrome */ | ||
| input[chrome-autofilled], |
Member
There was a problem hiding this comment.
Add a comment here to explain why non-stand chrome-autofilled is used.
Contributor
There was a problem hiding this comment.
NAB, but yes I agree, and as you said earlier:
autofill is a standard. chrome-autofilled is not.
Member
Screenshots🔲 iOS / native
🔲 iOS / Chrome
🔲 MacOS / Desktop
🔲 MacOS / ChromeScreen.Recording.2023-12-01.at.5.05.19.PM.mov🔲 Android / Chrome
🔲 Android / native
|
Member
|
@tienifr Let's get that comment so that it can be merged today. |
Member
|
bump @tienifr |
Contributor
Author
|
updated |
Comment on lines
+77
to
+78
| /* Chrome on iOS does not support the autofill pseudo class because it is a non-standard webkit feature. | ||
| We should rely on the chrome-autofilled property that being added to the input when users use auto-fill function */ |
Member
There was a problem hiding this comment.
This comment is wrong. autofill is a standard. chrome-autofilled & -webkit-autofill is not.
Suggested change
| /* Chrome on iOS does not support the autofill pseudo class because it is a non-standard webkit feature. | |
| We should rely on the chrome-autofilled property that being added to the input when users use auto-fill function */ | |
| /* Chrome on iOS use iOS's WKWebView, and WKWebView doesn't support non-standard webkit features. We have to rely on the chrome-autofilled attribute that being added to the input when users use auto-fill function */ |
Contributor
There was a problem hiding this comment.
I agree with the suggestion, but also remove "that" here We have to rely on the chrome-autofilled attribute that being added => We have to rely on the chrome-autofilled attribute being added, also when users use auto-fill function => when users use auto-fill
parasharrajat
approved these changes
Dec 4, 2023
Member
parasharrajat
left a comment
parasharrajat
left a comment
There was a problem hiding this comment.
Reviewer Checklist
- I have verified the author checklist is complete (all boxes are checked off).
- I verified the correct issue is linked in the
### Fixed Issuessection above - I verified testing steps are clear and they cover the changes made in this PR
- I verified the steps for local testing are in the
Testssection - I verified the steps for Staging and/or Production testing are in the
QA stepssection - I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
- I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
- I verified the steps for local testing are in the
- I checked that screenshots or videos are included for tests on all platforms
- I included screenshots or videos for tests on all platforms
- I verified tests pass on all platforms & I tested again on:
- Android / native
- Android / Chrome
- iOS / native
- iOS / Safari
- MacOS / Chrome / Safari
- MacOS / Desktop
- If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
- I verified proper code patterns were followed (see Reviewing the code)
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e.
toggleReportand notonIconClick). - I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g.
myBool && <MyComponent />. - I verified that comments were added to code that is not self explanatory
- I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- I verified any copy / text shown in the product is localized by adding it to
src/languages/*files and using the translation method - I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the
Waiting for Copylabel for a copy review on the original GH to get the correct copy. - I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in
STYLE.md) were followed
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e.
- If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
- I verified that this PR follows the guidelines as stated in the Review Guidelines
- I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like
Avatar, I verified the components usingAvatarhave been tested & I retested again) - I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
- I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
- If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately and each prop has a
/** comment above it */ - The file is named correctly
- The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
- The only data being stored in the state is data necessary for rendering and nothing else
- For Class Components, any internal methods passed to components event handlers are bound to
thisproperly so there are no scoping issues (i.e. foronClick={this.submit}the methodthis.submitshould be bound tothisin the constructor) - Any internal methods bound to
thisare necessary to be bound (i.e. avoidthis.submit = this.submit.bind(this);ifthis.submitis never passed to a component event handler likeonClick) - All JSX used for rendering exists in the render method
- The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
- If any new file was added I verified that:
- The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
- If a new CSS style is added I verified that:
- A similar style doesn't already exist
- The style can't be created with an existing StyleUtils function (i.e.
StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)
- If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
- If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like
Avataris modified, I verified thatAvataris working as expected in all cases) - If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
- If a new page is added, I verified it's using the
ScrollViewcomponent to make it scrollable when more elements are added to the page. - If the
mainbranch was merged into this PR after a review, I tested again and verified the outcome was still expected according to theTeststeps. - I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.
🎀 👀 🎀 C+ reviewed
Member
|
There is a pending suggestion also. |
neil-marcellini
requested changes
Dec 4, 2023
Contributor
neil-marcellini
left a comment
neil-marcellini
left a comment
There was a problem hiding this comment.
Looks great, good to go after we fix up the comment.
Comment on lines
+77
to
+78
| /* Chrome on iOS does not support the autofill pseudo class because it is a non-standard webkit feature. | ||
| We should rely on the chrome-autofilled property that being added to the input when users use auto-fill function */ |
Contributor
There was a problem hiding this comment.
I agree with the suggestion, but also remove "that" here We have to rely on the chrome-autofilled attribute that being added => We have to rely on the chrome-autofilled attribute being added, also when users use auto-fill function => when users use auto-fill
Contributor
Author
|
@neil-marcellini Fixed. Thank you |
Member
|
@tienifr The main comment suggestion is here #32332 (comment). @neil-marcellini suggested improvement over it. let's fix it. |
neil-marcellini
approved these changes
Dec 5, 2023
Contributor
neil-marcellini
left a comment
neil-marcellini
left a comment
There was a problem hiding this comment.
One NAB for the comment.
| } | ||
|
|
||
| /* Customizes the background and text colors for autofill inputs in Chrome */ | ||
| input[chrome-autofilled], |
Contributor
There was a problem hiding this comment.
NAB, but yes I agree, and as you said earlier:
autofill is a standard. chrome-autofilled is not.
Contributor
|
We can fix the comment in a follow up. |
74 tasks
Contributor
|
🚀 Deployed to staging by https://github.com/neil-marcellini in version: 1.4.9-0 🚀
|
1 similar comment
Contributor
|
🚀 Deployed to staging by https://github.com/neil-marcellini in version: 1.4.9-0 🚀
|
6 tasks
Contributor
|
🚀 Deployed to production by https://github.com/yuwenmemon in version: 1.4.9-5 🚀
|
6 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Details
Fixed Issues
$ #31415
PROPOSAL: #31415 (comment)
Tests
Offline tests
Same as above
QA Steps
PR Author Checklist
### Fixed Issuessection aboveTestssectionOffline stepssectionQA stepssectiontoggleReportand notonIconClick)myBool && <MyComponent />.src/languages/*files and using the translation methodWaiting for Copylabel for a copy review on the original GH to get the correct copy.STYLE.md) were followedAvatar, I verified the components usingAvatarare working as expected)/** comment above it */thisare necessary to be bound (i.e. avoidthis.submit = this.submit.bind(this);ifthis.submitis never passed to a component event handler likeonClick)StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))Avataris modified, I verified thatAvataris working as expected in all cases)ScrollViewcomponent to make it scrollable when more elements are added to the page.mainbranch was merged into this PR after a review, I tested again and verified the outcome was still expected according to theTeststeps.Screenshots/Videos
Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
iOS: mWeb Chrome
original-1F4A31B1-7136-4936-9F3D-0CE3F87AC142.mp4
MacOS: Chrome / Safari
Screen.Recording.2023-12-01.at.14.10.13.mov
MacOS: Desktop
Screen.Recording.2023-12-01.at.14.14.05.mp4