-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
[$500] Web - Chat - "Fire" is missing from the suggested emojis #35199
Comments
Job added to Upwork: https://www.upwork.com/jobs/~01bb30dd161d0ef71b |
Triggered auto assignment to @laurenreidexpensify ( |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @mananjadhav ( |
We think that this bug might be related to #vip-vsb |
ProposalPlease re-state the problem that we are trying to solve in this issue.The fire emoji is missing in mini context menu What is the root cause of that problem?We are slicing the fire emoji here
What changes do you think we should make in order to solve the problem?Change 3 to 4 to add fire emoji
CONST.QUICK_REACTIONS.slice(0, 4)
What alternative solutions did you explore? (Optional)If we don't want to add fire emoji then we can remove it from another menu too for consistency |
ProposalPlease re-state the problem that we are trying to solve in this issue.Web - Chat - "Fire" is missing from the suggested emojis What is the root cause of that problem?Actually, judging by this ticket, it looks as expected But decision about this ticket depends on the design team We have 2 places where we use QUICK_REACTIONS
![]()
![]() What changes do you think we should make in order to solve the problem?So to fix this issue we have 2 ways 1. Return 4 emojis For this we need delete slice like in second place
As a result code will look like :
2. Make 3 emojis in all places For this we need delete slice like in second place
And delete fourth emoji from QUICK_REACTIONS Lines 1666 to 1669 in ac94dc5
What alternative solutions did you explore? (Optional)NA |
cc @Expensify/design |
Hmm yeah, cc @dubielzyk-expensify @JmillsExpensify in case this was related to some of the mini menu improvements that were made recently. Was it intentional to remove the fire emoji? |
And also what would be the expected behavior? Do we want to maintain consistency? or do nothing? |
I don't think this is a bug. I think this is an intended update as part of the comment action menu updates we recently rolled out. Here's a mock from the Figma file/design doc: |
Like Danny said, yep it's part of us reducing the amount of cognetive load and therefor less items. One had to go sadly. I think at a later stage we'll allow to chose your favorite 3 like Slack does or just put the most commonly used |
@laurenreidexpensify Based on the comments above, best we close this one out? |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: 1.4.31.1
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4237630&group_by=cases:section_id&group_id=292106&group_order=asc
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Action Performed:
Expected Result:
"Fire" emoji should be visible.
Actual Result:
"Fire" is missing from the suggested emojis. It's still available if you right click a message.
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6355175_1706219360659.bandicam_2024-01-25_20-38-18-598.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: