-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
[$250] Composer - Composer box is refocused when Copying Link on Web and Desktop #45204
Comments
Triggered auto assignment to @lschurr ( |
@lschurr FYI 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 |
We think that this bug might be related to #vip-vsb |
Job added to Upwork: https://www.upwork.com/jobs/~01a3374b61f565b9cf |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @situchan ( |
I'm the author of #44399. That's our bad not to note a precondition for the composer to automatically refocus: it must already be focused before interacting with the context menu. So this is not a valid bug considering the current expectations. We can still change the expectations but should note that this is not a regression. Thanks. |
Edited by proposal-police: This proposal was edited at 2024-08-05 18:25:46 UTC. ProposalPlease re-state the problem that we are trying to solve in this issue.The composer is NOT refocused What is the root cause of that problem?When a report is focused, we set the composer focus callback with App/src/pages/home/report/ReportActionCompose/ComposerWithSuggestions/ComposerWithSuggestions.tsx Lines 589 to 591 in a19ef98
When we click on the copy link, we call
What changes do you think we should make in order to solve the problem?We should keep track the composer is focused or not when we open the context menu. Then we pass it as payload data when we open the context menu.
The test branch here https://github.com/nkdengineer/App/tree/fix/45204 What alternative solutions did you explore? (Optional)If we want to not focus on the composer after we select the context menu action in mWeb, we can add
App/src/pages/home/report/ReportActionCompose/ComposerWithSuggestions/ComposerWithSuggestions.tsx Lines 589 to 591 in a19ef98
App/src/pages/home/report/ReportActionCompose/ComposerWithSuggestions/ComposerWithSuggestions.tsx Lines 206 to 208 in 5af66e0
|
So the expected behavior is to refocus always on all platforms regardless of pre-focus status? |
I think it's expected. |
Any update @situchan? Are we saying this is expected and not a bug? |
I am saying this is not worth fixing. @Expensify/design what do you think of #45204 (comment)? |
Hmm interesting one for sure. My first reaction is that I don't think I would expect the composer to be refocused after using the Copy link menu item. The user is basically electing to tap outside of the composer box... so I don't think we should assume that they want to head back into the composer box immediately after interacting with a different part of the app. Curious what Danny and Jon think though! |
At the same time, if we only have two places (iOS and Android) where we aren't doing this behavior, I can see where it makes sense to make everything consistent so we have the same exact behavior on all platforms. |
Totally agree with this 100%.
Personally I think it makes more sense to not refocus the input on any platform after an action like this... but that might just be my personal preference On mobile, the keyboard takes up so much space and sometimes it can be hard to remove focus from the composer (and get the keyboard to go away). And trying to browse a conversation with the keyboard up is pretty frustrating. So I think I would still prefer not auto-focusing the composer. Just |
Thanks for the feedback.
|
I'm with Danny on this one. I don't think it makes that much sense to do on mobile due to the keyboard popping up. On desktop you got two input methods (keyboard and mouse) and focusing the composer doesn't break any flow or require a dismissal so that's fine for me. But on mobile, I just think it'd be more disruptive |
Updated proposal #45204 (comment) with new expected behavior. |
Cool cool, thanks to you both for your thoughts - I like where you landed. |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
Still looking for proposals |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
Not overdue |
Issue not reproducible during KI retests. (First week) |
Hey @situchan - Are you able to reproduce this one still? |
@lschurr, @srikarparsi, @situchan Eep! 4 days overdue now. Issues have feelings too... |
OP is outdated. This is final expected behavior. |
still reproducible on v9.0.31-22 web.mp4 |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
Issue not reproducible during KI retests. (Second week) |
Not overdue |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@lschurr, @srikarparsi, @situchan Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
I'm OOO until next week - Did we come to a decision about this one @srikarparsi? |
@lschurr, @srikarparsi, @situchan 6 days overdue. This is scarier than being forced to listen to Vogon poetry! |
Just followed up in the thread |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@lschurr, @srikarparsi, @situchan 8 days overdue is a lot. Should this be a Weekly issue? If so, feel free to change it! |
Closing, as we closed #vib-vsb, this is an edge case bug and not a near-term priority. |
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: 9.0.6-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers): applausetester+en@applause.expensifail.com
Issue reported by: Applause - Internal Team
Issue found when executing PR #44399
Action Performed:
Expected Result:
User doesn't expect the composer to get refocused.
Actual Result:
Composer gets refocussed: Expected chart
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6538235_1720636352340.Composer_is_not_refocused.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @situchanThe text was updated successfully, but these errors were encountered: