-
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] iOS Hybrid - Composer - Keyboard does not reopen after dismissing the context menu #50830
Comments
Triggered auto assignment to @flodnv ( |
💬 A slack conversation has been started in #expensify-open-source |
👋 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:
|
So, not a blocker right? |
sorry, my mistake. |
Job added to Upwork: https://www.upwork.com/jobs/~021846522126717879513 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @Ollyws ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.The keyboard does not reopen after dismissing the context menu What is the root cause of that problem?When users press + button, we will blur the composer
Even we have the logic to refocus in App/src/pages/home/report/ReportActionCompose/ComposerWithSuggestions/ComposerWithSuggestions.tsx Line 677 in 4a25c36
but it's prevented by App/src/pages/home/report/ReportActionCompose/ComposerWithSuggestions/ComposerWithSuggestions.tsx Lines 669 to 671 in 4a25c36
-> the focus logic doesn't run What changes do you think we should make in order to solve the problem?Since we don't want to call focus when the modal get closed App/src/pages/home/report/ReportActionCompose/ComposerWithSuggestions/ComposerWithSuggestions.tsx Lines 666 to 668 in 4a25c36
-> we shouldn't blur it if We can update onAddActionPressed
What alternative solutions did you explore? (Optional)We face the same issue when users long press on report action so we can apply the same solution in
|
@daledah any idea which PR caused this? |
@flodnv If we decide to hide the keyboard, we can refactor/remove this hook App/src/pages/home/report/ReportActionCompose/ComposerWithSuggestions/ComposerWithSuggestions.tsx Line 655 in 4a25c36
since it's used to |
@rezkiy37 Should we remove this hook #50830 (comment) |
Just to clarify: this is the expected result.
So I don't think we should touch something. So just close the issue. |
Thanks for the clarification and details @rezkiy37, I agree with you 👍 |
That why I think we can remove this hook. It's used to re-focus, but you change App/src/pages/home/report/ReportActionCompose/ComposerWithSuggestions/ComposerWithSuggestions.tsx Lines 666 to 668 in 4a25c36
|
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: 9.0.49-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: N/A
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause - Internal Team
Action Performed:
Expected Result:
The keyboard will reopen after dismissing the context menu (production behavior and staging mweb behavior)
Actual Result:
The keyboard does not reopen after dismissing the context menu
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6635613_1729019252899.ScreenRecording_10-16-2024_03-02-03_1.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @OllywsThe text was updated successfully, but these errors were encountered: