-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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] BUG: when flipping between chats, the composer box is gone and only the skeleton UI shows. #11962
Comments
Triggered auto assignment to @PauloGasparSv ( |
Triggered auto assignment to @MitchExpensify ( |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @rushatgabhane ( |
Current assignee @mountiny is eligible for the External assigner, not assigning anyone new. |
This can definitely be external issue, the UI jumps are not great, lets make sure it is spotless |
Proposal: Issue: App/src/pages/home/ReportScreen.js Line 297 in fbf0334
that is rendered by a conditional logic to check the Loading effect in the app. Solution: From:
To:
|
@chauchausoup nice and simple! i like that you've mentioned the cause as well. |
@mountiny let's go ahead with @chauchausoup's proposal 🎀 👀 🎀 C+ reviewed |
📣 @chauchausoup You have been assigned to this job by @mountiny! |
Thank you for the review @rushatgabhane, can you please raise a PR @chauchausoup ? |
Sure @mountiny will spin it in few hours. |
PR is in a review. |
@rushatgabhane Can you confirm if the regression would be avoided in here? Thank you for looking into this 🙇 |
😬 Thank you for confirming @rushatgabhane and thanks for pointing this out @0xmiroslav @chauchausoup can you think of a way how to prevent the regression from happening and solving this issue? Otherwise I am afraid we will have to open this for new proposals. |
So a way to move forward could be close this issue and the linked PR in favor of #11856 |
Oh perfect, @rushatgabhane, thanks! I think we can close this one then, since it is duplicate and the other issue has higher reward. I am sorry @chauchausoup this did not work out, thank you so much for your efforts but we cannot proceed with that proposal given it would introduce regression. |
I dint understand whats happening. How do it cause regression when my proposal is not even deployed? |
My proposal was posted earlier than @0xmiroslav 's right? |
@chauchausoup sorry for the confusion. You can read this comment, the solution you have proposed is a revert of a PR which fixed a regression. Rushat has confirmed that your PR is experiencing the issue so it would cause a regression unfortunately. I realize you have proposed solution earlier however, since this solution has a bug, the next proposal which avoids it goes forward. Apologies for this. |
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:
Composer window should not disappear
Actual Result:
composer window disappears between chats and the UI jumping around.
Workaround:
Unknown
Platform:
Where is this issue occurring?
Version Number: 1.2.17-1
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:
Recording.716.mp4
Expensify/Expensify Issue URL:
Issue reported by: @shawnborton
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1666030320048069
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: