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

Enlarge emojis in other contexts than just single character messages #47547

Open
wants to merge 54 commits into
base: main
Choose a base branch
from

Conversation

VickyStash
Copy link
Contributor

@VickyStash VickyStash commented Aug 16, 2024

Details

This is another try to merge the PR related to emojis enlarging, the previous one was reverted.

Fixed Issues

$ #4114
Potentially fixing #14753
PROPOSAL: N/A

Tests

  • Verify that no errors appear in the JS console

Composer:

  1. Draft a message (of any length) with text and emojis
  2. Verify that emojis are larger (17px) compared to the default size for text (15px) in the composer (emojis + text input)

Report history:

  1. Send a message with emojis and text
  2. Verify that emojis are larger (17px) compared to the default size for text (15pt) in the chat history and vertically centered with respect to eachother, such that the baseline of the emoji is below the plain text and the middle of the text vertically aligns with the middle of the emoji [$1000] Make emojis larger in other contexts than just single character messages #4114 (comment)

Settings:

  1. Go to Settings -> Profile and add emoji to your last name
  2. Verify that emoji appear larger (17px) than the rest of the text (15pt) in the text input
  3. Save the changes
  4. Open LHP
  5. Verify that emoji in user's last name appear larger (25px) compared to the rest of the text (22px)

Offline tests

Same as in the Tests section.

QA Steps

  • Verify that no errors appear in the JS console

Same as in the Tests section.

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

android1
android3
android2

Android: mWeb Chrome

android_web1
android_web3
android_web2

iOS: Native

ios1
ios3
ios2

iOS: mWeb Safari

ios_web3
ios_web1
ios_web2

MacOS: Chrome / Safari web1 web3 web2
MacOS: Desktop

desktop1
desktop3
desktop2

Copy link

melvin-bot bot commented Aug 20, 2024

Hey! I see that you made changes to our Form component. Make sure to update the docs in FORMS.md accordingly. Cheers!

@VickyStash VickyStash changed the title [WIP] Enlarge emojis in other contexts than just single character messages Enlarge emojis in other contexts than just single character messages Aug 21, 2024
@VickyStash VickyStash marked this pull request as ready for review August 21, 2024 10:08
@VickyStash VickyStash requested review from a team as code owners August 21, 2024 10:08
@melvin-bot melvin-bot bot requested review from parasharrajat and removed request for a team August 21, 2024 10:08
Copy link

melvin-bot bot commented Aug 21, 2024

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

# Conflicts:
#	src/components/Composer/index.native.tsx
#	src/pages/home/report/comment/TextCommentFragment.tsx
@parasharrajat
Copy link
Member

@VickyStash One bug and needs merge main.

@parasharrajat
Copy link
Member

I will be on leave till 25th oct. I will wrap up the Checklist afterwards.

@VickyStash
Copy link
Contributor Author

@parasharrajat In Chrome it looks bigger too, see the comparison of dev/prod:
DEV:
dev

PROD:
prod

@shawnborton
Copy link
Contributor

Let us know when the next round of screenshots are ready for review!

@pecanoro
Copy link
Contributor

@VickyStash Would be possible to check if this PR will fix this issue? Thank you!

@VickyStash
Copy link
Contributor Author

@VickyStash Would be possible to check if this PR will fix this #14753? Thank you!

@pecanoro No, unfortunately, it's not. I was able to reproduce the issue.

Screenshot

image

@VickyStash
Copy link
Contributor Author

I'm going to be OOO Oct 31 - Nov 3 🌴

# Conflicts:
#	src/pages/home/report/comment/TextCommentFragment.tsx
@parasharrajat
Copy link
Member

I will run another round of testing in sometime.

@shawnborton
Copy link
Contributor

How is this one going? Looks like we have some merge conflicts now...

# Conflicts:
#	src/components/AccountSwitcher.tsx
#	src/libs/ValidationUtils.ts
@VickyStash
Copy link
Contributor Author

I've resolved conflicts, kind bump @parasharrajat

@VickyStash
Copy link
Contributor Author

@parasharrajat any ETA on taking a look at this one?

@parasharrajat
Copy link
Member

I will get this done on 3 hours.

@parasharrajat
Copy link
Member

BUG: Android: Cursor is smaller on next line but pressing space increases its size.

Expected: Cursor should remain bigger when composer contains all emojies.

13.11.2024_20.41.13_REC.mp4

@parasharrajat
Copy link
Member

BUG: Similiar issue on web #47547 (comment).

13.11.2024_22.59.20_REC.mp4

@VickyStash
Copy link
Contributor Author

@parasharrajat @shawnborton Is it really an issue? I see slack acts the same for example:

slack_example.mp4

Fixing it can be tricky a little and cause some side issues. So I just want to confirm we really want to do it.

@parasharrajat
Copy link
Member

I would say not a big deal. This does not occur on iOS.

@VickyStash
Copy link
Contributor Author

Oh, we have conflicts again. I'm going to resolve them soon, though this one can be tricky.

@shawnborton
Copy link
Contributor

Cool, I think it's okay to let it slide. Let's get this one over the finish line though, we're so close!

# Conflicts:
#	src/components/Composer/implementation/index.tsx
#	src/libs/ComposerUtils/updateIsFullComposerAvailable.ts
@VickyStash
Copy link
Contributor Author

@parasharrajat Take a look, please 🙏

@parasharrajat
Copy link
Member

Running through checklist now.

@parasharrajat
Copy link
Member

Screenshots

🔲 iOS / native

15.11.2024_23.43.00_REC.mp4

🔲 iOS / Safari

15.11.2024_23.40.24_REC.mp4

🔲 MacOS / Desktop

15.11.2024_23.34.58_REC.mp4

🔲 MacOS / Chrome

15.11.2024_22.41.34_REC.mp4

🔲 Android / Chrome

15.11.2024_23.45.10_REC.mp4

🔲 Android / native

15.11.2024_23.37.17_REC.mp4

Copy link
Member

@parasharrajat parasharrajat left a comment

Choose a reason for hiding this comment

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

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 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(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 form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label 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.

🎀 👀 🎀 C+ reviewed

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.

8 participants