fix Fallback avatar background and selection highlight have the same color #43077

tienifr · 2024-06-04T22:12:58Z

Details

Fixed Issues

$ #39909 (comment)
PROPOSAL:

Tests

Open app
Go to FAB > Start chat
Enter a new email address
There will be distinctive color between the fallback avatar background and the selection highlight

Verify that no errors appear in the JS console

Offline tests

QA Steps

Verify that no errors appear in the JS console

PR Author Checklist

I linked the correct issue in the ### Fixed Issues section above
I wrote clear testing steps that cover the changes made in this PR
- I added steps for local testing in the Tests section
- I added steps for the expected offline behavior in the Offline steps section
- I added steps for Staging and/or Production testing in the QA steps section
- I added steps to cover 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 tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
I included screenshots or videos for tests on all platforms
I ran the tests on all platforms & verified they passed on:
- Android: Native
- Android: mWeb Chrome
- iOS: Native
- iOS: mWeb Safari
- MacOS: Chrome / Safari
- MacOS: Desktop
I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
I followed proper code patterns (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. toggleReport and not onIconClick)
- 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
  - If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
- 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 either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
- 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
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I followed the guidelines as stated in the Review Guidelines
I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
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
I verified that if a function's arguments changed that all usages have also been updated correctly
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(theme.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 Avatar is modified, I verified that Avatar is 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 the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label and/or tagged @Expensify/design so the design team can review the changes.
If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

output.mp4

MacOS: Desktop

Screen.Recording.2024-06-05.at.05.13.50.mov

…color

melvin-bot · 2024-06-04T22:16:39Z

@rushatgabhane 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]

tienifr · 2024-06-04T22:17:49Z

@rushatgabhane Please ignore this PR. @Santhosh-Sellavel will review it

shawnborton · 2024-06-05T06:15:19Z

src/styles/index.ts

@@ -1782,7 +1782,7 @@ const styles = (theme: ThemeColors) =>
        },

        sidebarLinkActive: {
-            backgroundColor: theme.buttonHoveredBG,
+            backgroundColor: theme.overlay,


Why are we using the overlay color here? That's not the correct color we should be using. For the active background color, we want to use product400 or the same color as our borders.

Ah. The overlay also has product400, but I just updated it to use activeComponentBG.

shawnborton · 2024-06-05T07:42:13Z

Perfect thanks!

…

On Wed, Jun 5, 2024 at 8:41 AM Tienifr ***@***.***> wrote: ***@***.**** commented on this pull request. ------------------------------ In src/styles/index.ts <#43077 (comment)>: > @@ -1782,7 +1782,7 @@ const styles = (theme: ThemeColors) => }, sidebarLinkActive: { - backgroundColor: theme.buttonHoveredBG, + backgroundColor: theme.overlay, Ah. The overlay also has product400, but I just updated it to use activeComponentBG. — Reply to this email directly, view it on GitHub <#43077 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AARWH5UDWEH26IYZW45KY4DZF2XKXAVCNFSM6AAAAABIZOHZ5GVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDAOJYGE3TAMJZGI> . You are receiving this because your review was requested.Message ID: ***@***.***>

rushatgabhane · 2024-06-19T08:38:43Z

Please ignore this PR. @Santhosh-Sellavel will review it

okayy. ignoring this PR

shawnborton · 2024-06-25T06:03:27Z

@rushatgabhane what's the latest here?

tienifr · 2024-06-25T09:08:49Z

@shawnborton No, @Santhosh-Sellavel will review this PR because he reviewed my original PR.

shawnborton · 2024-06-25T09:26:33Z

Okay, let’s try to get this one over the finish line. Thanks!

…

On Tue, Jun 25, 2024 at 11:09 AM Tienifr ***@***.***> wrote: @shawnborton <https://github.com/shawnborton> No, @Santhosh-Sellavel <https://github.com/Santhosh-Sellavel> will review this PR because he reviewed my original PR. — Reply to this email directly, view it on GitHub <#43077 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AARWH5TN4B66ZNHIPTZBHSTZJEXTPAVCNFSM6AAAAABIZOHZ5GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBYGM3TOOBYGU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

rushatgabhane · 2024-06-26T18:47:04Z

@tienifr maybe @Santhosh-Sellavel is OOO, so I'll take care of this for GSD's sake

i reached out to them on slack yesterday

https://expensify.enterprise.slack.com/archives/C02NK2DQWUX/p1719350602109949

rushatgabhane · 2024-06-26T18:49:43Z

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 Issues section 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 Tests section
- I verified the steps for Staging and/or Production testing are in the QA steps section
- 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 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: mWeb Chrome
- iOS: Native
- iOS: mWeb 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. toggleReport and not onIconClick).
- 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 either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
- 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
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 using Avatar have 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 this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
- Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
- 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(theme.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 Avatar is modified, I verified that Avatar is 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 the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label and/or tagged @Expensify/design so the design team can review the changes.
If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

my sim for mweb android is broken

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

shawnborton · 2024-06-26T19:02:43Z

All you @grgia !

tienifr · 2024-06-28T12:10:24Z

@grgia Can you help review this PR?

OSBotify · 2024-06-28T12:39:16Z

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

OSBotify · 2024-07-03T20:00:12Z

🚀 Deployed to staging by https://github.com/grgia in version: 9.0.4-0 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅

OSBotify · 2024-07-04T22:12:39Z

🚀 Cherry-picked to staging by https://github.com/tgolen in version: 9.0.4-5 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

OSBotify · 2024-07-10T10:55:05Z

🚀 Deployed to production by https://github.com/Julesssss in version: 9.0.5-13 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅

OSBotify · 2024-07-15T20:18:20Z

🚀 Deployed to production by https://github.com/thienlnam in version: 9.0.6-8 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅

fix Fallback avatar background and selection highlight have the same …

88ff231

…color

tienifr marked this pull request as ready for review June 4, 2024 22:16

tienifr requested review from a team as code owners June 4, 2024 22:16

melvin-bot bot requested review from rushatgabhane and removed request for a team June 4, 2024 22:16

shawnborton reviewed Jun 5, 2024

View reviewed changes

fix use activeComponentBG instead

625cb59

tienifr mentioned this pull request Jun 5, 2024

[HOLD for payment 2024-07-17][$250] Fallback avatar- The background of fallback avatar has the same color as selection highlight #39909

Closed

6 tasks

tienifr mentioned this pull request Jun 25, 2024

[$250] Wrong color is used for the active LHN item #44355

Closed

6 tasks

rushatgabhane approved these changes Jun 26, 2024

View reviewed changes

melvin-bot bot requested a review from grgia June 26, 2024 18:58

shawnborton approved these changes Jun 26, 2024

View reviewed changes

grgia approved these changes Jun 28, 2024

View reviewed changes

grgia merged commit cb8fce8 into Expensify:main Jun 28, 2024
17 of 18 checks passed

github-actions bot mentioned this pull request Jul 3, 2024

Deploy Checklist: New Expensify 2024-07-03 #44782

Closed

gijoe0295 mentioned this pull request Jul 4, 2024

[HOLD for payment 2024-08-29] [$125] Start chat - Add to group button has same color as background #44796

Closed

6 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

fix Fallback avatar background and selection highlight have the same color #43077

fix Fallback avatar background and selection highlight have the same color #43077

tienifr commented Jun 4, 2024 •

edited

Loading

melvin-bot bot commented Jun 4, 2024

tienifr commented Jun 4, 2024

shawnborton Jun 5, 2024

tienifr Jun 5, 2024

shawnborton commented Jun 5, 2024 via email

rushatgabhane commented Jun 19, 2024

shawnborton commented Jun 25, 2024

tienifr commented Jun 25, 2024

shawnborton commented Jun 25, 2024 via email

rushatgabhane commented Jun 26, 2024 •

edited

Loading

rushatgabhane commented Jun 26, 2024 •

edited

Loading

shawnborton commented Jun 26, 2024

tienifr commented Jun 28, 2024

OSBotify commented Jun 28, 2024

OSBotify commented Jul 3, 2024

OSBotify commented Jul 4, 2024

OSBotify commented Jul 10, 2024

OSBotify commented Jul 15, 2024

fix Fallback avatar background and selection highlight have the same color #43077

fix Fallback avatar background and selection highlight have the same color #43077

Conversation

tienifr commented Jun 4, 2024 • edited Loading

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

melvin-bot bot commented Jun 4, 2024

tienifr commented Jun 4, 2024

shawnborton Jun 5, 2024

Choose a reason for hiding this comment

tienifr Jun 5, 2024

Choose a reason for hiding this comment

shawnborton commented Jun 5, 2024 via email

rushatgabhane commented Jun 19, 2024

shawnborton commented Jun 25, 2024

tienifr commented Jun 25, 2024

shawnborton commented Jun 25, 2024 via email

rushatgabhane commented Jun 26, 2024 • edited Loading

rushatgabhane commented Jun 26, 2024 • edited Loading

Reviewer Checklist

Screenshots/Videos

shawnborton commented Jun 26, 2024

tienifr commented Jun 28, 2024

OSBotify commented Jun 28, 2024

OSBotify commented Jul 3, 2024

OSBotify commented Jul 4, 2024

OSBotify commented Jul 10, 2024

OSBotify commented Jul 15, 2024

tienifr commented Jun 4, 2024 •

edited

Loading

rushatgabhane commented Jun 26, 2024 •

edited

Loading

rushatgabhane commented Jun 26, 2024 •

edited

Loading