-
Notifications
You must be signed in to change notification settings - Fork 3k
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] Android narrow/low pixel tablets - Chat - The FAB button disappears or is covered by the keyboard in horizontal #12592
Comments
Triggered auto assignment to @jliexpensify ( |
Reassigning to Kadie as I'm about to head OOO |
Asking for someone with an iPad to reproduce - https://expensify.slack.com/archives/C01GTK53T8Q/p1668402566426039 |
Current assignee @kadiealexander is eligible for the External assigner, not assigning anyone new. |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @mananjadhav ( |
Triggered auto assignment to @iwiznia ( |
@iwiznia this is one of the oldest issues in the /App repo. To help us clear out the large backlog of bugs, can you:
|
I think this is a good example of why we should simply block rotation on native and review once we've actually reached reunification. |
I agree. |
@Julesssss @iwiznia Do we want to disable rotation on native in this issue? I was going to close based on our discussion in the community, but we can also use this issue to prevent rotation bugs by disabling this action. |
Yeah, I think that makes sense. |
We disabled rotation years ago. I don't think we need to make any changes |
I am confused, then how did @kbecciv reproduced this if rotation is disabled? |
So I take that back, we unlocked rotation for tablets at some point. |
I have a PR here #13043 If you agree, let's close this. |
Assigning myself as well since we lost the BZ assignment somehow. Also chiming in on @iwiznia's question above.
Hmm, yeah I'm with you. I tried to reproduce this on my iPad mini and I wasn't able to. So I think I'm with you, we should close this. In fact, I'll do that but ahead of doing so I will update the title to remove iPad for clarity. |
To clarify, it's reproducible on older/smaller ipads. |
This is still reproducible in latest version of android. So I suggest to reopen this issue and put on hold until #13106 is merged |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. 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. |
@0xmiroslav for clarity, is it reproducible on non-tablets or just tablets? Reason being, we don't officially support tablets, though I'm more than happy to re-open if you think it's going to be fixed anyway. |
This happens on android tablets with small size as explained in issue title |
Ok yeah, so all those are unsupported devices. In the interest of focus, let's just keep this closed. We need to tackle tablet support one day, but now isn't the time. |
I agree with @JmillsExpensify. We're focused on items such as BugZero, WAQ, and Dark theme, etc. Tablets isn't the focus right now, and I think we should tackle tablets sometime in future. |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Issue found when executing PR #12345
Action Performed:
Expected Result:
The FAB button shouldn't floats to the top and sticks above the keyboard
Actual Result:
The FAB button disappears or is covered by the keyboard
Workaround:
Unknown
Platform:
Where is this issue occurring?
Version Number: 1.2.25.0
Reproducible in staging?: Yes
Reproducible in production?: Yes
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Bug5813586_12345_Android.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal team
Slack conversation:
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: