-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[HOLD for payment 2023-10-10] [$500] Web - Inconsistency bug: App adds space after emoji in composer box but does not add space after emoji in edit #27195
Comments
Job added to Upwork: https://www.upwork.com/jobs/~0195c2171640e5c29b |
Triggered auto assignment to @mallenexpensify ( |
Bug0 Triage Checklist (Main S/O)
|
Triggered auto assignment to @trjExpensify ( |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @eVoloshchak ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.Web - Inconsistency bug: App adds space after emoji in composer box but does not add space after emoji in edit What is the root cause of that problem?We are not adding spaces captured by emoji when we are setting selection. App/src/pages/home/report/ReportActionItemMessageEdit.js Lines 183 to 194 in 7f2cf16
What changes do you think we should make in order to solve the problem?We need to add spaces captured by emojis with newDraft length and then subtract it.
Result:fixed.mp4 |
ProposalPlease re-state the problem that we are trying to solve in this issue.There's an inconsistency between the compose and edit boxes. When typing out an emoji there is sometimes a space after and sometimes not. What is the root cause of that problem?There is a difference in the way the selection pointer is calculated in the ReportActionItemMessageEdit editor box vs the ComposerWithSuggestions composer box. Editor: App/src/pages/home/report/ReportActionItemMessageEdit.js Lines 183 to 192 in 7f2cf16
Composer: App/src/pages/home/report/ReportActionCompose/ComposerWithSuggestions.js Lines 186 to 194 in 7f2cf16
Note the Composer uses the ComposerUtils.getCommonSuffixLength to calculate the cursor position. What changes do you think we should make in order to solve the problem?By utilizing the same ComposerUtils.getCommonSuffixLength function inside of the editor box, the cursor position is calculated correctly. Recording.2023-09-11.174251.mp4What alternative solutions did you explore? (Optional)We could also create a separate helper function so that we do not use "composer" utils alongside an editor component, however, it would be a duplication of code. |
I was assigned second, dropping off. |
@Krishna2323 I tried your code but it seems to set the cursor to the wrong position if you insert an emoji in the middle of text while editing, depending on if you "complete" the emoji either inside or outside of the colons. Recording.2023-09-11.180706.mp4 |
@neg-0, yes you are correct, my solution is not correct. |
@mallenexpensify You're right! Fortunately the helper function from ComposerUtils works in all cases! |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
Reviewing this tomorrow as a first priority |
I think we should proceed with @neg-0's proposal
I agree that would be redundant, ideally we should use a single method for both of these (which is exactly what this proposal achieves) 🎀👀🎀 C+ reviewed! |
📣 @dhanashree-sawant 🎉 An offer has been automatically sent to your Upwork account for the Reporter role 🎉 Thanks for contributing to the Expensify app! |
@eVoloshchak @youssef-lr PR has been submitted! #28297 |
Based on my calculations, the pull request did not get merged within 3 working days of assignment. Please, check out my computations here:
On to the next one 🚀 |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.76-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2023-10-10. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
For reference, here are some details about the assignees on this issue:
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
|
Requested the $500 payment via NewDot |
Issue reporter: @dhanashree-sawant paid $50 via Upwork @eVoloshchak err on the side of proposing to create regression tests because QA/Applause keeps a separate doc/list of edge cases they check once a month. Thx |
$500 payment approved for @eVoloshchak based on summary above. |
Regression Test Proposal
Do we agree 👍 or 👎 |
Re-opening for the regression test. |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Action Performed:
Expected Result:
App should either not add space after emoji in compose box or add space after emoji in edit box to maintain consistency
Actual Result:
App adds space after emoji in compose box and does not add space after emoji in edit box
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.67.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:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
no.space.after.emoji.in.edit.mp4
Recording.4402.mp4
Expensify/Expensify Issue URL:
Issue reported by: @dhanashree-sawant
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1694176420343339
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: