[HOLD for payment 2024-06-20] [$250] Mark down - Copying and pasting part of a code block doesn't work

[izarutskaya]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: 1.4.82-0
Reproducible in staging?: Y
Reproducible in production?: N
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team

Action Performed:

1. Navigate to staging.new.expensify.com
2. Open any chat report
3. Send a code block using opening three back ticks and closing three back ticks at the end
4. Select part of the sent code block and press ctrl + c to copy and paste it on the compose box

Expected Result:

The copied code block is pasted

Actual Result:

Nothing gets pasted in the compose box

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6510462_1718180975471.bandicam_2024-06-12_11-25-03-468.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01bd2b97089b315a6c
• Upwork Job ID: 1800965003148739899
• Last Price Increase: 2024-06-12

Issue Owner

Current Issue Owner: @

Issue Owner

Current Issue Owner: @alexpensify

[melvin-bot]

Triggered auto assignment to @danieldoglas (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

Triggered auto assignment to @alexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[izarutskaya]

@alexpensify I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.

[danieldoglas]

I think this was caused by #43270

Reverting that PR solved the issue for me locally.

[danieldoglas]

@mollfpr @rlinoz @SzymczakJ can you please check what's going on here? Seems related to #43270

[rlinoz]

Indeed reverting the PR fixes it

[rlinoz]

Not adding the excludeStyles as a dependency here https://github.com/Expensify/App/pull/43270/files#diff-a1120b846ebeebcc99d15542e13bd9537c273751a97bce6a0de03295ec98d2baR89 fixes it, but I don't understand why

[SzymczakJ]

On it. I'll try to find solution ASAP

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~01bd2b97089b315a6c

[melvin-bot]

Current assignee @situchan is eligible for the External assigner, not assigning anyone new.

[alexpensify]

Ok, I've updated the assignments here to reflect everyone who is helping to address this issue.

[danieldoglas]

Removing blocker label since it was CP'd

[melvin-bot]

Reviewing label has been removed, please complete the "BugZero Checklist".

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.82-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• [CP Staging] Fix code blocks paste bug #43594

If no regressions arise, payment will be issued on 2024-06-20. 🎊

For reference, here are some details about the assignees on this issue:

• @SzymczakJ does not require payment (Contractor)
• @situchan requires payment (Needs manual offer from BZ)

[melvin-bot]

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:

• [@situchan] The PR that introduced the bug has been identified. Link to the PR:
• [@situchan] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
• [@situchan] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
• [@situchan] Determine if we should create a regression test for this bug.
• [@situchan] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
• [@alexpensify] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

[melvin-bot]

Payment Summary

Upwork Job

• Contributor: @SzymczakJ is from an agency-contributor and not due payment
• ROLE: @situchan paid $250 via Upwork (LINK)

BugZero Checklist (@alexpensify)

• I have verified the correct assignees and roles are listed above and updated the neccesary manual offers
• I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants/1800965003148739899/hired)
• I have paid out the Upwork contracts or cancelled the ones that are incorrect
• I have verified the payment summary above is correct

[alexpensify]

@situchan - I've sent over an offer via Upwork. Please accept, and then I can complete the payment process. Thanks!

[melvin-bot]

@danieldoglas, @alexpensify, @SzymczakJ, @situchan Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[alexpensify]

All set here, I've completed the payment process. All actions are complete here -- closing!