-
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
[$2000] Content off screen and keyboard opens when navigating to default rooms #8292
Comments
Triggered auto assignment to @Beamanator ( |
Triggered auto assignment to @adelekennedy ( |
Looks like a good issue to be solved externally 👍 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @rushatgabhane ( |
Triggered auto assignment to @tgolen ( |
Still waiting for proposals |
time to DOUBLE! |
And it's time to double again |
It's time to double again! |
ProposalRemove the autoFocus, when the room has just been created (no action history) OverviewWhat is causing this issue, is when you open a room, and there is no action on that report, except the "CREATED"
as you can see in this line, the autoFocus is being tiggered by SolutionRemoves the This will change the behavior of having the autofocus when you open a room without any previous action. but it will keep consistency with other rooms that have already an action history (list of messages). |
Looking at it now. |
@parasharrajat I have raised a PR upstream to add the drawer events feature. I just don't know what the maintainer thinks about those events. if those get accepted. I believe it will be easier to implement in the app. Thank you! |
I don't think they will be interested to look into this issue that you tagged on that PR. |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a production regression has occurred a Root Cause Analysis is required. Please follow the instructions here. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
Where do we stand with the proposal on this? I like the idea of getting those events put into the upstream code, but what does that mean for this issue in the meantime? Are we going to place it on hold, or move forward with |
Some time back, due to a lack of proper fix, we decided on slack to ignore the focus on the mobile web platforms. But then the issue received a new proposal claiming to achieve it as well. I looked at a different issue where the same DrawerProgress based proposal was being discussed and so far the conclusion on that issue is suggesting to implement this kind of change upstream #9253 (comment). Meanwhile, @mdneyazahmad created a new PR that tries to implement the new drawer animation events on react-navigation. I am following that as well. Latest update on the other issue: - #9253 (comment). I will wait a few more days and see if we have to move forward with DrawerProgress implementation. |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a production regression has occurred a Root Cause Analysis is required. Please follow the instructions here. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
latest update #9253 (comment) |
Issue not reproducible during KI retests. (Second week) |
the other issue is on now put on HOLD #9253 (comment). |
Issue not reproducible during KI retests. (Third week) |
I'm going to go ahead and close this |
@adelekennedy just checking, did we get @parasharrajat paid out for this (context) |
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:
Expected Result:
Navigating to a default room shows the chat content within the page
Actual Result:
Navigating to a default room shows the chat content half off screen and the keyboard opens
Issue is repro when no chats in the room
Workaround:
unknown
Platform:
Where is this issue occurring?
Version Number: 1.1.44-3
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: Any additional supporting documentation
Expensify/Expensify Issue URL:
Issue reported by: @neil-marcellini
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1647980292349759
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: