-
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
[$1000] Chat - Composer Not focused when clicking on composer box #25892
Comments
Triggered auto assignment to @MitchExpensify ( |
Bug0 Triage Checklist (Main S/O)
|
ProposalPlease re-state the problem that we are trying to solve in this issue.Composer Not focused when clicking on composer box What is the root cause of that problem?In the ReportActionItemMessageEdit component, we have a callback when Emoji picker modal is hidden, it will focus back to the editing report message App/src/pages/home/report/ReportActionItemMessageEdit.js Lines 379 to 382 in 34d4e54
So even if we click focus on the main composer, by above callback, it will focus back to the editing report message What changes do you think we should make in order to solve the problem?In the above onModalHide callback, we need to check if the main composer is focusing, we will early exit and won't focus back to the editing report message Result: Screen.Recording.2023-08-25.at.16.49.54.mov |
Job added to Upwork: https://www.upwork.com/jobs/~0161d746e7dbb99cde |
Current assignee @MitchExpensify is eligible for the External assigner, not assigning anyone new. |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @parasharrajat ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.Composer Not focused when clicking on composer box What is the root cause of that problem?When Emoji picker modal is closed, it will focus back to the edit composer regardless of any user interaction: App/src/pages/home/report/ReportActionItemMessageEdit.js Lines 379 to 382 in 253db32
So even if we click focus on the main compose, it will always focus back to the edit compose. What changes do you think we should make in order to solve the problem?Update: As previously discussed here, we should move all Since PR #24481, we have a way to re-focus on the "right" compose:
onModalHide={() => {
ReportActionComposeFocusManager.focus();
}}
onFocus={() => {
...
ReportActionComposeFocusManager.onComposerFocus(() => {
if (!willBlurTextInputOnTapOutside) {
return;
}
focus(true);
});
}}
|
OK. Thanks for the proposals. My intuition is asking to hold this issue as we have done for #23403. Even though solutions might not overlap they seem quite related. Also, I was checking on #24481 and the implementation doesn't seem very scalable. This is out of the scope of this issue but we can pursue improving that as well. |
Isn’t this an expected behaviour? When the EmojiPicker is displayed, we do not allow interactions with any other element in Report Screen until it is dismissed. A tap on anywhere else other than the EmojiPicker will hide and bring the focus back on the currently edited message input. |
That was the behavior a few months back but it seems that it is recently changed. I am not sure where. |
@parasharrajat do you still think this is the best course of action here?
|
The reason behind this is that a single PR caused these issues and C+ can pick a more complete solution in #23403 to fix the issue completely. I am monitoring the review of the other issue. If it seems that we are not solving this issue there, I will continue here. Does that sound good? or do you want me to continue on this issue? |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
This sounds great to me! Thank you |
Sounds like @tienifr's proposal is updated and ready for you @parasharrajat |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
Bump @parasharrajat, can you please provide an update? Thanks! |
After PRs related to #24452 were merged, this issue is still reproducible. I'll take a look and update in our PR. |
Thanks @tienifr. Ping me when you have next update. |
@tienifr Any updates? |
@tienifr, please provide an update. I will DM you for visibility. Thanks! |
@isabelastisser we continued our work in the PR ^ |
@tienifr @parasharrajat will the PR be merged soon? |
@isabelastisser PR is back in review. |
No updates yet, I see that we're still reviewing the PR. |
@parasharrajat, any news? |
PR awaiting Engineer review. |
It should be ready to be paid in 2 days. |
Payment summary:
|
@parasharrajat, can you please confirm that the payment summary is correct? Thanks! |
@isabelastisser I think payment for @tienifr would be same as 1K. |
Payment requested as per #25892 (comment) |
@parasharrajat, do we need a regression test? |
Do we have a BZ checklist for this issue? |
I will add that soon. Please proceed with payment @JmillsExpensify |
Sorry I'm unable to, as that would fail our financial controls. |
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 StepsWeb & Desktop
=====
=====
=====
=====
mWeb & Android & iOS
=====
=====
=====
=====
Do you agree 👍 or 👎 ? |
@JmillsExpensify Done. |
Thanks! $1,000 approved for @parasharrajat |
|
@johnmlee101, can you please review the test proposal when you have a chance? Thanks! |
LGTM! |
All set! |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Action Performed:
Expected Result:
Clicking on the main composer box focuses the composer
Actual Result:
Clicking on the main composer box focuses on the main composer for a second and then focuses on the edit Composer
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.57-1
Reproducible in staging?: Yes
Reproducible in production?: Yes
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
T106-1_EditComposerFocus.mp4
Gravar.2966.mp4
Expensify/Expensify Issue URL:
Issue reported by: @daveSeife
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1692048812228079
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: