Skip to content
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

feat: arrow navigation in context menu #27877

Merged
merged 19 commits into from
Sep 22, 2023
Merged

feat: arrow navigation in context menu #27877

merged 19 commits into from
Sep 22, 2023

Conversation

samh-nl
Copy link
Contributor

@samh-nl samh-nl commented Sep 20, 2023

Details

Navigating the report actions context menu with arrows was not previously possible.

Fixed Issues

$ #23280
PROPOSAL: #23280 (comment)

Tests

Web/desktop

  1. Go to any report that has a message
  2. Right-click the message
  3. Verify the context menu opens
  4. Press the down arrow once
  5. Verify the first menu item ('Reply in thread') is selected
  6. Verify that you can navigate through the entire menu by pressing the up and down arrows
  7. Use the arrows to go to the first menu item
  8. Press Enter
  9. Verify the page navigates to a thread and the context menu closes

Mobile

  1. Go to any report that has a message
  2. Long-press the message
  3. Verify that the context menu opens
  • Verify that no errors appear in the JS console

Offline tests

Web/desktop

  1. Go to any report that has a message
  2. Right-click the message
  3. Verify the context menu opens
  4. Press the down arrow once
  5. Verify the first menu item ('Reply in thread') is selected
  6. Verify that you can navigate through the entire menu by pressing the up and down arrows
  7. Use the arrows to go to the first menu item
  8. Press Enter
  9. Verify the page navigates to a thread and the context menu closes

Mobile

  1. Go to any report that has a message
  2. Long-press the message
  3. Verify that the context menu opens

QA Steps

Web/desktop

  1. Go to any report that has a message
  2. Right-click the message
  3. Verify the context menu opens
  4. Press the down arrow once
  5. Verify the first menu item ('Reply in thread') is selected
  6. Verify that you can navigate through the entire menu by pressing the up and down arrows
  7. Use the arrows to go to the first menu item
  8. Press Enter
  9. Verify the page navigates to a thread and the context menu closes

Mobile

  1. Go to any report that has a message
  2. Long-press the message
  3. Verify that the context menu opens
  • 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 / Chrome
    • iOS / native
    • iOS / 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 approved by marketing by adding the Waiting for Copy label 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
  • 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 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
    • If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
    • 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(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 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 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 author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web
Web.Screen.Recording.2023-09-20.at.18.26.03.mov
Mobile Web - Chrome
mWeb.Chrome.webm
Mobile Web - Safari
mWeb.Safari.screencap-2023-09-20T165102.236Z.mp4
Desktop
Desktop.Screen.Recording.2023-09-20.at.18.27.06.mov
iOS
Native.iOS.screencap-2023-09-20T165350.509Z.mp4
Android
Native.Android.webm

@samh-nl samh-nl requested a review from a team as a code owner September 20, 2023 18:07
@melvin-bot melvin-bot bot requested review from situchan and removed request for a team September 20, 2023 18:08
@melvin-bot
Copy link

melvin-bot bot commented Sep 20, 2023

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

@samh-nl
Copy link
Contributor Author

samh-nl commented Sep 20, 2023

For mobile, where there's no arrows, I have added to the test steps to verify that the context menu opens as expected when long-pressing. Let me know if you think I should change it.

@samh-nl
Copy link
Contributor Author

samh-nl commented Sep 21, 2023

Thank you, I have accepted both suggestions.

@situchan
Copy link
Contributor

Also, please pull main

@situchan
Copy link
Contributor

unit test failing

Also, found the case of arrows not working on LHN context menu while focusing on composer

Screen.Recording.2023-09-21.at.7.17.56.PM.mov

@samh-nl
Copy link
Contributor Author

samh-nl commented Sep 21, 2023

Also, found the case of arrows not working on LHN context menu while focusing on composer

We prevent losing composer focus when clicking on an LHN item (here).
The intention behind it relates to left-clicks, not right-clicks that cause a context menu, but we don't check for that.

I think we need to have a similar handling as in EmojiReactionBubble (here) and check if e.button === 2, to ensure that the composer loses focus when the context menu opens. That solves the problem and makes it consistent with opening context menu elsewhere (report action context menu, FAB, etc all cause composer to lose focus).

@situchan
Copy link
Contributor

I was about to say it's out of scope. There's already GH to blur composer when any popover is open - #25485

@situchan
Copy link
Contributor

Please investigate why unit test is failing

@samh-nl
Copy link
Contributor Author

samh-nl commented Sep 21, 2023

Good find, perhaps then it is better to leave it for that issue as they are taking a broader approach which would make my solution redundant.

@samh-nl
Copy link
Contributor Author

samh-nl commented Sep 21, 2023

recheck

Copy link
Contributor

@situchan situchan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

triggering actions

@situchan
Copy link
Contributor

@samh-nl please revert full code and see it still happens

@samh-nl
Copy link
Contributor Author

samh-nl commented Sep 21, 2023

I see this particular unit test is also failing in another recent PR: https://github.com/Expensify/App/actions/runs/6261808769/job/17002648235?pr=27941

@samh-nl
Copy link
Contributor Author

samh-nl commented Sep 21, 2023

Could revert, but if you check the accepted suggestions: one of them caused the error, the other one didn't, so it's a bit random (it measures execution time). If the error doesn't occur after reverting, it might just be luck.

@situchan
Copy link
Contributor

yes, let's try. Hope that "luck" won't happen

@situchan
Copy link
Contributor

pass. now re-revert

@situchan
Copy link
Contributor

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 / 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. 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 approved by marketing by adding the Waiting for Copy label 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
  • 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(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 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 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

Web
web.mov
Mobile Web - Chrome
Mobile Web - Safari
msafari.mov
Desktop
desktop.mov
iOS
ios.mov
Android

@situchan
Copy link
Contributor

situchan commented Sep 21, 2023

Another weird behavior:

Screen.Recording.2023-09-21.at.9.25.06.PM.mov

Enter key triggers 2 actions at the same time

@samh-nl
Copy link
Contributor Author

samh-nl commented Sep 21, 2023

Also occurs when right-clicking an avatar. Focus is put on the element. Let me check how to solve this, shouldPreventDefault is already default true.

@samh-nl
Copy link
Contributor Author

samh-nl commented Sep 21, 2023

Here's my solution: The shouldPreventDefault is not enough, what it needs is event.stopPropagation();
For this, we could add a new config called shouldStopPropagation (default false, so it doesn't change any of the existing behavior), it would be placed here.

And then in our usage of useKeyboardShortcut, we add shouldStopPropagation: true to the configuration.

@samh-nl
Copy link
Contributor Author

samh-nl commented Sep 21, 2023

I see in the callback we pass the event, so instead of adding a new config, what also works is to add it like this:

useKeyboardShortcut(
        CONST.KEYBOARD_SHORTCUTS.ENTER,
-        () => {
+        (event) => {
+            // Ensures the event does not cause side-effects beyond the context menu, e.g. when an outside element is focused
+            event.stopPropagation();

@situchan
Copy link
Contributor

ok, that looks good. Thanks for the research

@samh-nl
Copy link
Contributor Author

samh-nl commented Sep 21, 2023

I have pushed the change

Copy link
Contributor

@situchan situchan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

@francoisl all yours

@melvin-bot melvin-bot bot requested a review from francoisl September 22, 2023 00:16
Copy link
Contributor

@francoisl francoisl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, minor small change request

src/components/ContextMenuItem.js Outdated Show resolved Hide resolved
@@ -89,6 +99,7 @@ function ContextMenuItem({onPress, successIcon, successText, icon, text, isMini,
descriptionTextStyle={styles.breakAll}
style={getContextMenuItemStyles(windowWidth)}
isAnonymousAction={isAnonymousAction}
focused={focused}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I also thought isFocused name is better but didn't request change because focused prop name already exists here 😄

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have adjusted the prop name in the added code.
If you'd like me to refactor the existing prop in MenuItem and change it there + it's usages also, let me know.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that's fine as we didn't touch MenuItem component here.
If anyone is adding/changing props on that component in the future, they might be responsible.
cc: @francoisl

Copy link
Contributor

@francoisl francoisl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@francoisl francoisl merged commit 33b3c88 into Expensify:main Sep 22, 2023
13 checks passed
@OSBotify
Copy link
Contributor

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

@situchan
Copy link
Contributor

situchan commented Sep 22, 2023

There's 2 hrs delay from bonus timeline but it would be much appreciated if it's still eligible unless any regression found.
The delay was just from variable name change and @samh-nl was sleeping at that moment.
cc: @francoisl

@OSBotify
Copy link
Contributor

🚀 Deployed to staging by https://github.com/francoisl in version: 1.3.73-0 🚀

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

@OSBotify
Copy link
Contributor

🚀 Deployed to production by https://github.com/mountiny in version: 1.3.73-1 🚀

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

@OSBotify
Copy link
Contributor

🚀 Deployed to staging by https://github.com/francoisl in version: 1.3.74-0 🚀

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

@OSBotify
Copy link
Contributor

🚀 Deployed to production by https://github.com/chiragsalian in version: 1.3.74-3 🚀

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants