[HOLD for payment 2023-02-15] [$2000] not able to select text of keyboard shortcuts when you open popup second time

[kavimuru]

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:

1. open app
2. go to settings > About > View Keyboard shortcuts
3. open the popup an close it
4. again open the popup and try to select text

Expected Result:

not able to select text when you open popup second time

Actual Result:

user should be able to select text

Workaround:

unknown

Platforms:

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

• MacOS / Chrome

Version Number: 1.2.47-0
Reproducible in staging?: y
Reproducible in production?: y
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:

Screen.Recording.2022-12-30.at.11.50.46.AM.mov

Recording.38.mp4

Expensify/Expensify Issue URL:
Issue reported by: @gadhiyamanan
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1672381522931449

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~0142c09828b956ad3b
• Upwork Job ID: 1613255747122876416
• Last Price Increase: 2023-02-01

[melvin-bot]

Triggered auto assignment to @joekaufmanexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[jasperhuangg]

Hey! Don't really think this needs to be fixed, @joekaufmanexpensify do you agree?

[sketchydroide]

this is a rather specific BUG, but one nonetheless, and acording to WAQ, if it't reproducable it's a Bug...
Also I can see reasons a user would like to copy paste keyboard shortcuts, namely to send it to another user so 🤷🏼
Oh and I can reproduce it to.

If you don't take it I will @jasperhuangg

[joekaufmanexpensify]

Yes, agreed. My understanding is if it's a reproducible bug, we will fix it. I actually raised this yesterday, and this is where we landed.

[joekaufmanexpensify]

Triaging:

From this SO: https://stackoverflow.com/c/expensify/questions/14418

• The "bug" is actually a bug: Y, confirmed here.
• The bug is not a duplicate report of an existing GH (close the GH and add any novel details to the original GH instead): N/A.
• The bug is reproducible, following the reproduction steps: Y.
• If you're unable to reproduce the bug, add the Needs reproduction label. Comment on the issue outlining the steps you took to try to reproduce the bug, your results and tag the issue reporter and the Applause QA member who created the issue. Ask them to clarify reproduction steps and/or to check the reproduction steps again. Close issue.: N/A
• The GH template is filled out as fully as possible -- this means the GH body and title are clear (ie. could an external contributor understand it and work on it?): Y.
• The GH was created by an Expensify employee or a QA tester: Y.
• If the bug is an OldDot issue, you should decide whether it is widespread enough to justify fixing or it is better to wait for reunification. If it's better to wait, close the GH & provide this justification: N/A.
• If there's a link to Slack, check the discussion to see if we decided not to fix it: N/A
• Decide if the GH should be resolved by an External contributor or Internal engineer, add the appropriate label:

[joekaufmanexpensify]

I can reproduce the fact that the text is not selectable on the second try here. Whether we want the text to be selectable, I am less sure. I am going to bring to Slack.

[joekaufmanexpensify]

Posted about this here.

[joekaufmanexpensify]

Bumped slack discussion.

[joekaufmanexpensify]

Still waiting for more discussion in Slack.

[joekaufmanexpensify]

Not overdue.