Delete emojis with several code points completely on "Backspace" press by c3024 · Pull Request #52995 · Expensify/App

c3024 · 2024-11-23T11:43:14Z

Explanation of Change

Pressing backspace does not remove some emojis (like Wales flag) completely on web browsers. This PR fixes that.

Fixed Issues

$ #51336
PROPOSAL: #51336 (comment)

Tests

Input Wales flag emoji ( 🏴󠁧󠁢󠁷󠁬󠁳󠁿 )in composer.
Press backspace.
Verify that the flag emoji is completely removed from the composer.

Verify that no errors appear in the JS console

Offline tests

Same as Tests.

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."

Same as Tests.

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

graphemeAndroid.mov

Android: mWeb Chrome

Screenrecorder-2024-11-23-17-49-33-862.mp4

iOS: Native

graphemeiOS.mov

iOS: mWeb Safari

RPReplay_Final1732364221.MP4

MacOS: Chrome / Safari

graphemeChrome.mov

graphemeSafari.mov

MacOS: Desktop

graphemeDesktop.mov

c3024 · 2024-11-23T12:37:58Z

+                }
+
+                // Grapheme segmentation is same for English and Spanish.
+                const splitter = new Intl.Segmenter(CONST.LOCALES.EN, {granularity: 'grapheme'});


I used Intl.Segmenter instead of grapheme-splitter because we are already using Intl namespace object in out repo. As per mdn, Intl.Segmenter works on all latest browsers and devices now.

c3024 · 2024-11-23T12:41:57Z

+
+                // Wales flag has 14 UTF-16 code units. This is the emoji with the largest number of UTF-16 code units we use.
+                const start = Math.max(0, selection.start - 14);
+                const graphemes = Array.from(splitter.segment(lastTextRef.current.substring(start, selection.start)));


Splitting only a few code units of the text, so I think there should not be any performance degradation.

melvin-bot · 2024-11-23T12:42:38Z

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

c3024 · 2024-12-11T05:36:19Z

@eVoloshchak , gentle bump!

eVoloshchak · 2024-12-29T17:55:36Z

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 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.ts 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.
For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
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

Screen.Recording.2025-01-06.at.03.05.06.mov

Android: mWeb Chrome

Screen.Recording.2025-01-06.at.03.07.37.mov

iOS: Native

Screen.Recording.2025-01-05.at.09.34.25.mov

iOS: mWeb Safari

Screen.Recording.2025-01-05.at.09.39.59.mov

MacOS: Chrome / Safari

Screen.Recording.2025-01-05.at.09.29.07.mov

MacOS: Desktop

Screen.Recording.2025-01-06.at.03.10.14.mov

eVoloshchak · 2024-12-29T17:57:58Z

@c3024, could you please merge with the latest main and I'll give this the last round of testing?

c3024 · 2024-12-30T03:30:20Z

@eVoloshchak , done. Please have a look!

eVoloshchak

LGTM!

OSBotify · 2025-01-07T14:46:25Z

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

github-actions · 2025-01-08T02:59:38Z

🚀 Deployed to staging by https://github.com/Gonals in version: 9.0.82-0 🚀

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

github-actions · 2025-01-08T03:39:27Z

🚀 Deployed to staging by https://github.com/Gonals in version: 9.0.82-0 🚀

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

github-actions · 2025-01-10T03:38:03Z

🚀 Deployed to production by https://github.com/thienlnam in version: 9.0.82-12 🚀

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

c3024 added 2 commits November 23, 2024 17:07

delete whole flag emoji on backspace press

638b428

fix lint

4f454c3

c3024 commented Nov 23, 2024

View reviewed changes

c3024 marked this pull request as ready for review November 23, 2024 12:42

c3024 requested a review from a team as a code owner November 23, 2024 12:42

melvin-bot Bot requested review from eVoloshchak and removed request for a team November 23, 2024 12:42

Christinadobrzyn mentioned this pull request Dec 2, 2024

[HOLD for payment 2025-01-17] [$250] Web - Emoji- Black box for flag emoji are difficult to cancel with backspace key #51336

Closed

8 tasks

Merge branch 'main' into remove-whole-flag-emoji-on-backspace-press

8249779

Merge branch 'main' into remove-whole-flag-emoji-on-backspace-press

8b5c724

eVoloshchak approved these changes Jan 6, 2025

View reviewed changes

melvin-bot Bot requested a review from Gonals January 6, 2025 02:11

Gonals approved these changes Jan 7, 2025

View reviewed changes

Gonals assigned c3024 Jan 7, 2025

Gonals merged commit 60aa36b into Expensify:main Jan 7, 2025

github-actions Bot mentioned this pull request Jan 8, 2025

Deploy Checklist: New Expensify 2025-01-08 #54928

Closed

60 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Delete emojis with several code points completely on "Backspace" press#52995

Delete emojis with several code points completely on "Backspace" press#52995
Gonals merged 4 commits into
Expensify:mainfrom
c3024:remove-whole-flag-emoji-on-backspace-press

c3024 commented Nov 23, 2024 •

edited

Loading

Uh oh!

c3024 Nov 23, 2024

Uh oh!

c3024 Nov 23, 2024

Uh oh!

melvin-bot Bot commented Nov 23, 2024

Uh oh!

c3024 commented Dec 11, 2024

Uh oh!

eVoloshchak commented Dec 29, 2024 •

edited

Loading

Uh oh!

eVoloshchak commented Dec 29, 2024

Uh oh!

c3024 commented Dec 30, 2024

Uh oh!

eVoloshchak left a comment

Uh oh!

OSBotify commented Jan 7, 2025

Uh oh!

github-actions Bot commented Jan 8, 2025

Uh oh!

github-actions Bot commented Jan 8, 2025

Uh oh!

github-actions Bot commented Jan 10, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Uh oh!

Conversation

c3024 commented Nov 23, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

c3024 Nov 23, 2024

Choose a reason for hiding this comment

Uh oh!

c3024 Nov 23, 2024

Choose a reason for hiding this comment

Uh oh!

melvin-bot Bot commented Nov 23, 2024

Uh oh!

c3024 commented Dec 11, 2024

Uh oh!

eVoloshchak commented Dec 29, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

eVoloshchak commented Dec 29, 2024

Uh oh!

c3024 commented Dec 30, 2024

Uh oh!

eVoloshchak left a comment

Choose a reason for hiding this comment

Uh oh!

OSBotify commented Jan 7, 2025

Uh oh!

github-actions Bot commented Jan 8, 2025

Uh oh!

github-actions Bot commented Jan 8, 2025

Uh oh!

github-actions Bot commented Jan 10, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

c3024 commented Nov 23, 2024 •

edited

Loading

eVoloshchak commented Dec 29, 2024 •

edited

Loading