-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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-08-16] [$1000] Selecting all and pasting into the composer prompts user to send an attachment. #18583
Comments
Triggered auto assignment to @sonialiap ( |
Bug0 Triage Checklist (Main S/O)
|
@sonialiap Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Reproducible
Screen.Recording.2023-05-18.at.9.28.51.PM.mov |
The linked PR is in production but this error still shows up so it didn't fix it. Adding External |
Job added to Upwork: https://www.upwork.com/jobs/~01b727a2688d7bb8a9 |
Current assignee @sonialiap is eligible for the External assigner, not assigning anyone new. |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @parasharrajat ( |
Triggered auto assignment to @techievivek ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.When pasting from a selection, it is showing the attachment dialog whenever an image is part of the selection. What is the root cause of that problem?A block of code inside Composer detects whether an image is contained within the HTML content. If an image exists, then it is treated as an attachment. What changes do you think we should make in order to solve the problem?We should detect whether or not text is a part of that HTML content and the plaintext content. If there is text, then we should paste that instead. We also need to check whether or not that text matches the alt text of the image, in which case, the image should be pasted. We can add the following in
When doing this, pasting any content that contains text will now paste the text into the Composer. What alternative solutions did you explore? (Optional)N/A |
@sonialiap Can you please reassign this issue to another engineer as Vivek is OOO? |
I can reproduce the same thing by copying GH comments, so IMO we can definitely improve the copy-paste logic here so it doesn't show an error. @parasharrajat, Interested to hear your thoughts on why you may have considered this issue not worth solving, if that was the case. |
@sonialiap @parasharrajat @techievivek this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks! |
I will continue this tomorrow. Didn't get time for this today. |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@techievivek Same as this comment https://expensify.slack.com/archives/C049HHMV9SM/p1684442056948549?thread_ts=1683394374.441039&cid=C049HHMV9SM. Also, the expected behavior is not clear to me. Can you please clarify the expected behavior if you think we should solve this? |
@parasharrajat I totally agree with the point that this issue may not be a critical concern, so perhaps we can consider closing it and prioritize more urgent bugs. But I think we can at least seek proposals to prevent showing the error message about not being able to fetch images. What do you think about it? |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.51-2 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-08-16. 🎊 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:
|
Issue not reproducible during KI retests. (Second week) |
Has this been paid out yet? I'd usually wait a little longer before raising this, but since the weekend's almost here, I thought I'd ask now. |
@Victor-Nyagudi It hasn't been paid out yet. |
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:
Regression Test Steps
Do you agree 👍 or 👎 ? |
@sonialiap Can you please post the summary as well as handle other payments? |
Bump @sonialiap. |
Bump @sonialiap... |
Any updates? @sonialiap |
Sorry guys, I was out. Sending offers out now
|
@sonialiap I've already received and accepted an offer from @Christinadobrzyn a few minutes ago for the reporting bonus. |
@sonialiap I was getting this error when I tried to apply: My upwork profile is here: https://www.upwork.com/freelancers/~012ec968f7113a1b63 |
@Victor-Nyagudi Feel free to reject the extra offer. |
@Victor-Nyagudi the offer process in upwork is
Christina did #1 and I finished off the #3. I did not send an extra offer, but let me know if you got paid twice :) |
@sonialiap I only got one offer, but the payment for the milestone hasn't been released yet. Am I missing something? |
@qispark thanks, offer sent! (bonus will be applied during payment step) @Victor-Nyagudi the payment was approved yesterday but I just ended the contract, maybe that was holding up the payment. Could you refresh and check if it's showing as released now? |
The payment has gone through now. Thank you. Strangely, I didn't get the confirmation of the milestone being approved yesterday, but everything's sorted out now. |
Thanks @sonialiap, I have accepted and requested a milestone payment now. |
Payment sent ✔️ |
Payment requested as per #18583 (comment) |
$1,500 payment for @parasharrajat approved based on BZ summary. |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
Expected Result:
All selected text is pasted into the composer.
Actual Result:
A new page/modal opens up prompting the user to send an attachment if you perform the steps above in a 1-on-1 chat. Clicking the "Send Attachment" button uploads the background shown on the page which appears in the chat and can be interacted with.
Until you select something else and copy it, pasting in the composer will open this page/modal, even if you're pasting in a different chat, whether that be a 1-on-1 or group chat.
However, if you perform the same steps in a group chat first, the selection is pasted but an error toast notification (see attached screenshot) briefly appears at the top right of the screen stating:
There was an error getting the image you posted.
Similarly, if you try pasting in a different chat after selecting all and copying from a group chat, the text will be pasted, but the error will also be shown, whether that be pasting in a subsequent group chat or 1-on-1.
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3. 11.2
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
Recording.183.1.mp4
expensify-mac-safari-copy-bug.mov
expensify-mac-desktop-copy-bug.mov
Recording.184.mp4
Expensify/Expensify Issue URL:
Issue reported by: @Victor-Nyagudi
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1683394374441039
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: