Skip to content
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

Closed
mvtglobally opened this issue Mar 24, 2022 · 143 comments
Closed
Assignees
Labels
Bug Something is broken. Auto assigns a BugZero manager. Engineering External Added to denote the issue can be worked on by a contributor Help Wanted Apply this label when an issue is open to proposals by contributors Weekly KSv2

Comments

@mvtglobally
Copy link

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:

  1. Create workspace
  2. Navigate to default room

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?

  • Mobile Web - Safari

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
IMG_0158D0729524-1

Expensify/Expensify Issue URL:
Issue reported by: @neil-marcellini
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1647980292349759

View all open jobs on GitHub

@melvin-bot
Copy link

melvin-bot bot commented Mar 24, 2022

Triggered auto assignment to @Beamanator (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

@Beamanator Beamanator removed their assignment Mar 24, 2022
@Beamanator Beamanator added the External Added to denote the issue can be worked on by a contributor label Mar 24, 2022
@melvin-bot
Copy link

melvin-bot bot commented Mar 24, 2022

Triggered auto assignment to @adelekennedy (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

@Beamanator
Copy link
Contributor

Looks like a good issue to be solved externally 👍

@adelekennedy
Copy link

Internal
External

@melvin-bot
Copy link

melvin-bot bot commented Mar 26, 2022

Triggered auto assignment to Contributor-plus team member for initial proposal review - @rushatgabhane (Exported)

@melvin-bot melvin-bot bot added the Help Wanted Apply this label when an issue is open to proposals by contributors label Mar 26, 2022
@melvin-bot
Copy link

melvin-bot bot commented Mar 26, 2022

Triggered auto assignment to @tgolen (Exported), see https://stackoverflow.com/c/expensify/questions/7972 for more details.

@mountiny mountiny changed the title Content off screen and keyboard opens when navigating to default rooms [$250] Content off screen and keyboard opens when navigating to default rooms Mar 31, 2022
@tgolen
Copy link
Contributor

tgolen commented Apr 4, 2022

Still waiting for proposals

@MelvinBot MelvinBot removed the Overdue label Apr 4, 2022
@adelekennedy
Copy link

time to DOUBLE!

@adelekennedy adelekennedy changed the title [$250] Content off screen and keyboard opens when navigating to default rooms [$500] Content off screen and keyboard opens when navigating to default rooms Apr 4, 2022
@adelekennedy
Copy link

And it's time to double again

@adelekennedy adelekennedy changed the title [$500] Content off screen and keyboard opens when navigating to default rooms [$1000] Content off screen and keyboard opens when navigating to default rooms Apr 12, 2022
@adelekennedy
Copy link

It's time to double again!

@adelekennedy adelekennedy changed the title [$1000] Content off screen and keyboard opens when navigating to default rooms [$2000] Content off screen and keyboard opens when navigating to default rooms Apr 18, 2022
@anboia
Copy link

anboia commented Apr 25, 2022

Proposal

Remove the autoFocus, when the room has just been created (no action history)

Overview

What is causing this issue, is when you open a room, and there is no action on that report, except the "CREATED" actionName, this enables autoFocus

autoFocus={this.shouldFocusInputOnScreenFocus || _.size(this.props.reportActions) === 1}

as you can see in this line, the autoFocus is being tiggered by _.size(this.props.reportActions) === 1 condition.

Solution

Removes the _.size(this.props.reportActions) === 1 condition, this will open the report screen without autofocusing the text input, and the issue will be gone.

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).

@tgolen

@parasharrajat
Copy link
Member

Looking at it now.

@mdneyazahmad
Copy link
Contributor

@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!

@parasharrajat
Copy link
Member

I don't think they will be interested to look into this issue that you tagged on that PR.
Instead, try to create a new issue on RN that is not related to this app and link that instead.

@melvin-bot
Copy link

melvin-bot bot commented Sep 16, 2022

⚠️ Looks like this issue was linked to a possible regression on PRODUCTION here

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.

@tgolen
Copy link
Contributor

tgolen commented Sep 27, 2022

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 DrawerProgress? I actually really like the look of DrawerProgress so I'd be cool with moving forward on that while we wait to see if we can get those events added upstream. If they ever get added upstream, then we can come back here and remove DrawerProgress eventually.

@melvin-bot melvin-bot bot removed the Overdue label Sep 27, 2022
@parasharrajat
Copy link
Member

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.

@melvin-bot
Copy link

melvin-bot bot commented Sep 30, 2022

⚠️ Looks like this issue was linked to a possible regression on PRODUCTION here

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.

@melvin-bot melvin-bot bot added the Overdue label Oct 6, 2022
@parasharrajat
Copy link
Member

latest update #9253 (comment)

@melvin-bot melvin-bot bot removed the Overdue label Oct 6, 2022
@melvin-bot melvin-bot bot added the Overdue label Oct 17, 2022
@mvtglobally
Copy link
Author

Issue not reproducible during KI retests. (Second week)

@parasharrajat
Copy link
Member

the other issue is on now put on HOLD #9253 (comment).

@melvin-bot melvin-bot bot removed the Overdue label Oct 18, 2022
@puneetlath puneetlath added the Bug Something is broken. Auto assigns a BugZero manager. label Oct 19, 2022
@mvtglobally
Copy link
Author

Issue not reproducible during KI retests. (Third week)

@melvin-bot melvin-bot bot added the Overdue label Oct 27, 2022
@tgolen
Copy link
Contributor

tgolen commented Oct 27, 2022

I'm going to go ahead and close this

@dylanexpensify
Copy link
Contributor

@adelekennedy just checking, did we get @parasharrajat paid out for this (context)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something is broken. Auto assigns a BugZero manager. Engineering External Added to denote the issue can be worked on by a contributor Help Wanted Apply this label when an issue is open to proposals by contributors Weekly KSv2
Projects
None yet
Development

No branches or pull requests