-
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
Main chat composer not visible on mobile web #8135
Comments
Triggered auto assignment to @Justicea83 ( |
Can't reproduce the error |
Triggered auto assignment to @kadiealexander ( |
@roryabraham, is this eligible for reporting? I had reported this earlier here. |
Actually I think this is not eligible for reporting simply because it's a regression we identified a long time ago and forgot to fix. That's probably why @parasharrajat marked it as a duplicate in Slack. I'll handle the revert myself as soon as I have a few spare cycles. |
Ah cool, thanks for the clarification 😃 . |
Sorry, this is a pretty simple fix (in that it's just a revert for now), but I just haven't gotten around to it yet. |
I actually can't reproduce this either. Going to close it – feel free to reopen if it's reproducible. |
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:
You should be able to see and type in the composer.
Actual Result:
The composer is automatically scrolled out of view.
Workaround:
unknown
Platform:
Where is this issue occurring?
Version Number: 1.1.42-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
RPReplay_Final1646964880.MP4
Expensify/Expensify Issue URL:
Issue reported by: @roryabraham
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1646964936524219
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: