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

[$1000] Make emojis larger in other contexts than just single character messages #4114

Open
jboniface opened this issue Jul 16, 2021 · 194 comments
Assignees
Labels
Design Engineering External Added to denote the issue can be worked on by a contributor NewFeature Something to build that is a new item. Weekly KSv2

Comments

@jboniface
Copy link

jboniface commented Jul 16, 2021

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!


This issue covers several related scenarios:

Scenario 1

Action Performed:

Add an emoji with other plain text characters in a message in the composer.

Expected Result:

The emoji should be larger (19pt) compared to the default size for text (15pt) in the composer. The emoji and text should appear 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 (like the right-hand-side of this example.

Actual Result:

The emoji is the same size as the rest of the text.

Scenario 2

Action Performed:

Send a message with emoji and text.

Expected Result:

The emoji should be larger (19pt) compared to the default size for text (15pt) in the chat history. The emoji and text should appear 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 (like the right-hand-side of this example

Actual Result:

The emoji is the same size as the rest of the text.

Scenario 3

Action Performed

Draft a message (of any length) with only emoji.

Expected Result

The emoji should appear very large (27pt) in the composer.

Actual Result

The emoji appear very small (15pt).

Scenario 4

Action Performed

Send a message (of any length) with only emoji.

Expected Result

The emoji should appear very large (27pt) in the report history.

Actual Result

The emoji only appear large in the report history if there is only one emoji in the message.

Scenario 5

Action Performed

Go to Settings -> Profile and add emoji(s) to your last name 😎

Expected Result

The emoji should appear larger (19pt) than the rest of the text (15pt) in the text input. The emoji and text should appear 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 (like the right-hand-side of this example

Actual Result

The emoji appear the same size as the text.

Scenario 6

Action Performed

  1. Go to Settings -> Profile and add emoji(s) to your last name 😎.
  2. Save your profile.
  3. Open the Settings RHP and look at your name:

Expected Result

The emoji should appear larger (21pt) than the rest of the text (17pt) in the text input. The emoji and text should appear 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 (like the right-hand-side of this example

Actual Result

The emoji and text have the same height:

image

Scenario 7

Action Performed

  1. Go to Settings -> Profile and add emoji(s) to your last name 😎.
  2. Save your profile.
  3. Open a chat with another user and send them a message. Take a look at your message in the report history.

Expected Result

The emoji should appear larger (19pt) than the rest of the test (15pt). The emoji and text should appear 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 (like the right-hand-side of this example

Actual Result

The emoji appears the same size as the rest of the text.

image

Workaround:

no

Platform:

all

View all open jobs on Upwork

Issue OwnerCurrent Issue Owner: @JmillsExpensify
@jboniface jboniface added the AutoAssignerTriage Auto assign issues for triage to an available triage team member label Jul 16, 2021
@MelvinBot
Copy link

Triggered auto assignment to @Christinadobrzyn (AutoAssignerTriage), see https://stackoverflow.com/c/expensify/questions/4749 for more details.

@MelvinBot MelvinBot removed the AutoAssignerTriage Auto assign issues for triage to an available triage team member label Jul 16, 2021
@rdjuric

This comment was marked as outdated.

@parasharrajat

This comment was marked as outdated.

@jboniface

This comment was marked as outdated.

@rdjuric

This comment was marked as outdated.

@MelvinBot
Copy link

Triggered auto assignment to @ctkochan22 (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

@Christinadobrzyn Christinadobrzyn removed their assignment Jul 28, 2021
@ctkochan22 ctkochan22 added the Improvement Item broken or needs improvement. label Aug 4, 2021
@ctkochan22 ctkochan22 removed their assignment Aug 4, 2021
@MelvinBot MelvinBot removed the Weekly KSv2 label Aug 27, 2021
@MelvinBot
Copy link

This issue has not been updated in over 15 days. eroding to Monthly issue.

P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!

@MelvinBot
Copy link

@jboniface, this Monthly task hasn't been acted upon in 6 weeks; closing.

If you disagree, feel encouraged to reopen it -- but pick your least important issue to close instead.

@mallenexpensify

This comment was marked as outdated.

@ctkochan22

This comment was marked as outdated.

@ctkochan22 ctkochan22 added the External Added to denote the issue can be worked on by a contributor label Mar 10, 2022
@MelvinBot
Copy link

Triggered auto assignment to @JmillsExpensify (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

@MelvinBot MelvinBot added the Daily KSv2 label Mar 10, 2022
@VickyStash
Copy link
Contributor

Okay nice, I think that can work. What do you think?

For me it looks okay as well. Also, that's doesn't look like super often case (sending the message with 20+ emojis only)

@JmillsExpensify
Copy link

Discussion on-going (Commenting to keep MelvinBot happy).

@melvin-bot melvin-bot bot removed the Overdue label Aug 14, 2024
@VickyStash
Copy link
Contributor

Updates:

  • I've implemented scenario 5 and 6
  • Tomorrow, I'll be OOO (15th Aug), but I think on Friday, I'll start the PR preparing/active testing on all of the platforms.

@VickyStash
Copy link
Contributor

Updates: I've started to prepare the Draft PR and testing over platforms

@melvin-bot melvin-bot bot added the Overdue label Aug 16, 2024
@VickyStash
Copy link
Contributor

Updates:
Continue to work on the Draft PR.
Today, I have tested the WEB platform. I've resolved the remaining TODO related to the correct comment text selection. Only one bug with composer height jumping/increasing when an emoji is entered is left on the WEB. I'll share my suggestions for its solutions tomorrow.

@VickyStash
Copy link
Contributor

Updates:
I've resolved all of the issues I've found for now and started to combine the PR. I still need to add screenshots and clean the code in several places. If everything goes as expected, I should be able to open the PR for review tomorrow.

@melvin-bot melvin-bot bot added Reviewing Has a PR in review Weekly KSv2 and removed Overdue Daily KSv2 labels Aug 21, 2024
@VickyStash
Copy link
Contributor

The PR has been opened for the review!

@parasharrajat
Copy link
Member

Update: PR is in review with a couple of bugs under fixing. Next update in next week.

@VickyStash
Copy link
Contributor

The latest updates can be found in the PR.

Note: I'm going to be OOO next week (Sept 16-20) 🌴

@tomekzaw
Copy link
Contributor

tomekzaw commented Sep 16, 2024

FYI Please bump react-native-live-markdown to 0.1.150 to include Expensify/react-native-live-markdown#491 that fixes "Unsupported type: inline-image" error on Android.

@parasharrajat
Copy link
Member

parasharrajat commented Sep 21, 2024

We should have the next update on Monday.

@VickyStash
Copy link
Contributor

Updates: We are waiting for this PR with react-native-live-markdown update to be merged so we can start another round of the review.

@VickyStash
Copy link
Contributor

Updates: The PR with react-native-live-markdown upgrade was reverted. But the new one has already been opened: #50047, so waiting for it. It's not possible to bumb the lib version outside of that PR cause inline images functionality was added in version 0.1.145.

@roryabraham
Copy link
Contributor

@francoisl choosing you at random to take this over while I'm on parental leave. Hope you don't mind 🙃

@roryabraham roryabraham removed Reviewing Has a PR in review Awaiting Payment Auto-added when associated PR is deployed to production labels Oct 4, 2024
@VickyStash
Copy link
Contributor

Updates: the PR is waiting for re-review.

@melvin-bot melvin-bot bot added the Overdue label Oct 30, 2024
@JmillsExpensify
Copy link

PRs in progress

@melvin-bot melvin-bot bot removed the Overdue label Oct 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Design Engineering External Added to denote the issue can be worked on by a contributor NewFeature Something to build that is a new item. Weekly KSv2
Projects
None yet
Development

No branches or pull requests