-
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
Comment - Pressing up key doesn't open editing composer on owned message #36173
Comments
👋 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:
|
Triggered auto assignment to @amyevans ( |
We think that this bug might be related to #vip-vsp |
https://expensify.slack.com/archives/C049HHMV9SM/p1707427624683799 let's assign SWM to this? |
Related to live markdown so taking over |
Thanks! |
The bug occurs because the live markdown input ref is missing the |
We've reverted the offending PR #35837, so this is no longer a blocker |
Tested on release |
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.39-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers): [email protected]
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Action Performed:
Expected Result:
Editing composer should be opened on owned message
Actual Result:
Editing composer is not opened on owned message
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6372431_1707420192667.Rename.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: