fix: clicking enter on emoji selector for status results in leaving status pane. #47761

Krishna2323 · 2024-08-20T23:19:37Z

Details

Fixed Issues

$ #47272
PROPOSAL: #47272 (comment)

Tests

Head to status
Click on emoji selector
Search for any emoji
When the emoji you want is auto-focused, hit enter
Verify the emoji is selected and input is focused

Verify that no errors appear in the JS console

Offline tests

Head to status
Click on emoji selector
Search for any emoji
When the emoji you want is auto-focused, hit enter
Verify the emoji is selected and input is focused

QA Steps

Head to status
Click on emoji selector
Search for any emoji
When the emoji you want is auto-focused, hit enter
Verify the emoji is selected and input is focused

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

android_Chrome.mp4

Android: mWeb Chrome

android_chrome_r.mp4

iOS: Native

ios_native.mp4

iOS: mWeb Safari

ios_safari.mp4

MacOS: Chrome / Safari

web_chrome.mp4

MacOS: Desktop

desktop_app.mp4

…tatus pane. Signed-off-by: krishna2323 <[email protected]>

melvin-bot · 2024-08-20T23:19:41Z

@rayane-djouah 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]

Krishna2323 · 2024-08-21T14:14:48Z

I'm facing one more bug where the selected emoji stays highlighted, I will fix that and update here soon.

Signed-off-by: krishna2323 <[email protected]>

Krishna2323 · 2024-08-23T13:30:38Z

I'm facing one more bug where the selected emoji stays highlighted, I will fix that and update here soon.

lol, this wasn't a bug, I fixed and found this was intentional and again reverted 🥲, I believe code changes are completed, I will update the in few hours.

Krishna2323 · 2024-08-23T15:25:30Z

@rayane-djouah, please start reviewing this when you have some time. Thanks

rayane-d · 2024-08-27T15:11:29Z

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

N/A

Android: mWeb Chrome

N/A

iOS: Native

N/A

iOS: mWeb Safari

N/A

MacOS: Chrome / Safari

Screen.Recording.2024-08-27.at.8.23.01.PM.mov

MacOS: Desktop

Screen.Recording.2024-08-27.at.8.22.26.PM.mov

rayane-d

LGTM and tests well

rayane-d · 2024-08-28T11:36:46Z

all yours @carlosmiceli

OSBotify · 2024-08-28T13:47:51Z

✋ 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-08-28T21:44:49Z

🚀 Deployed to staging by https://github.com/carlosmiceli in version: 9.0.26-1 🚀

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

OSBotify · 2024-08-30T18:33:16Z

🚀 Deployed to production by https://github.com/puneetlath in version: 9.0.26-6 🚀

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

ahmedGaber93 · 2024-11-06T22:07:33Z

src/components/EmojiPicker/EmojiPickerMenu/index.tsx

-                if ('types' in item || 'name' in item) {
-                    const emoji = typeof preferredSkinTone === 'number' && item?.types?.[preferredSkinTone] ? item?.types?.[preferredSkinTone] : item.code;
-                    onEmojiSelected(emoji, item);
-                }
                // On web, avoid this Enter default input action; otherwise, it will add a new line in the subsequently focused composer.
                keyBoardEvent.preventDefault();


Moving Enter login to useKeyboardShortcut and Keeping prevent default and stop propagation here cause this issue #50561, and we fixed it here #50971

fix: clicking enter on emoji selector for status results in leaving s…

fa2b75e

…tatus pane. Signed-off-by: krishna2323 <[email protected]>

Krishna2323 requested a review from a team as a code owner August 20, 2024 23:19

melvin-bot bot requested a review from rayane-d August 20, 2024 23:19

melvin-bot bot removed the request for review from a team August 20, 2024 23:19

Krishna2323 marked this pull request as draft August 21, 2024 10:49

Krishna2323 added 3 commits August 23, 2024 16:54

Merge branch 'Expensify:main' into krishna2323/issue/47272

dc54e4f

fix: emoji highlighted when opening status emoji picker.

3102c71

Signed-off-by: krishna2323 <[email protected]>

revert changes.

7c8e35e

Signed-off-by: krishna2323 <[email protected]>

Merge branch 'Expensify:main' into krishna2323/issue/47272

052cbf4

Krishna2323 marked this pull request as ready for review August 23, 2024 15:25

rayane-d approved these changes Aug 27, 2024

View reviewed changes

melvin-bot bot requested a review from carlosmiceli August 27, 2024 19:26

carlosmiceli approved these changes Aug 28, 2024

View reviewed changes

carlosmiceli merged commit 6697c26 into Expensify:main Aug 28, 2024
16 of 17 checks passed

github-actions bot mentioned this pull request Aug 28, 2024

Deploy Checklist: New Expensify 2024-08-28 #48221

Closed

93 tasks

mallenexpensify mentioned this pull request Aug 31, 2024

[HOLD for Payment 2024-09-6][$250] clicking enter on emoji selector for status results in leaving status pane #47272

Closed

6 tasks

ahmedGaber93 reviewed Nov 6, 2024

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

fix: clicking enter on emoji selector for status results in leaving status pane. #47761

fix: clicking enter on emoji selector for status results in leaving status pane. #47761

Krishna2323 commented Aug 20, 2024 •

edited

Loading

melvin-bot bot commented Aug 20, 2024

Krishna2323 commented Aug 21, 2024

Krishna2323 commented Aug 23, 2024

Krishna2323 commented Aug 23, 2024

rayane-d commented Aug 27, 2024 •

edited

Loading

rayane-d left a comment

rayane-d commented Aug 28, 2024

OSBotify commented Aug 28, 2024

OSBotify commented Aug 28, 2024

OSBotify commented Aug 30, 2024

ahmedGaber93 Nov 6, 2024

fix: clicking enter on emoji selector for status results in leaving status pane. #47761

fix: clicking enter on emoji selector for status results in leaving status pane. #47761

Conversation

Krishna2323 commented Aug 20, 2024 • edited Loading

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

melvin-bot bot commented Aug 20, 2024

Krishna2323 commented Aug 21, 2024

Krishna2323 commented Aug 23, 2024

Krishna2323 commented Aug 23, 2024

rayane-d commented Aug 27, 2024 • edited Loading

Reviewer Checklist

Screenshots/Videos

rayane-d left a comment

Choose a reason for hiding this comment

rayane-d commented Aug 28, 2024

OSBotify commented Aug 28, 2024

OSBotify commented Aug 28, 2024

OSBotify commented Aug 30, 2024

ahmedGaber93 Nov 6, 2024

Choose a reason for hiding this comment

Krishna2323 commented Aug 20, 2024 •

edited

Loading

rayane-d commented Aug 27, 2024 •

edited

Loading