-
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
[HOLD for payment 2023-10-31] [HOLD for payment 2023-10-30] [$500] Scroll is not working properly on the distance detail page, it sometimes gets stuck when scrolling up and down #29038
Comments
Job added to Upwork: https://www.upwork.com/jobs/~01348e03e4994bab90 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @Ollyws ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.Scroll is briefly blocked when trying to scroll to the distance details page, or IOU page with receipt. The issue can be better replicated using the trackpad
What is the root cause of that problem?The problem comes from the container of the
<View style={[StyleUtils.getReportWelcomeContainerStyle(isSmallScreenWidth), StyleUtils.getMinimumHeight(CONST.EMPTY_STATE_BACKGROUND.MONEY_REPORT.MIN_HEIGHT)]}>
<AnimatedEmptyStateBackground />
</View> The style What changes do you think we should make in order to solve the problem?I suggest removing the What alternative solutions did you explore? (Optional)The issue comes partially from the <Animated.Image
pointerEvents="box-none"
source={EmptyStateBackgroundImage}
style={[StyleUtils.getReportWelcomeBackgroundImageStyle(isSmallScreenWidth), animatedStyles]}
/> N/A |
ProposalPlease re-state the problem that we are trying to solve in this issue.Scroll is not working properly on the Money request view page. What is the root cause of that problem?The root cause of the issue is that we're defining a min height for the empty state background image container without adding a appropriate margin on the child components in What changes do you think we should make in order to solve the problem?We should follow the same pattern as defined here and try to replicate in the This involves replacing this with:
ResultScreen.Recording.2023-10-07.at.4.19.48.AM.movScreen.Recording.2023-10-07.at.4.20.44.AM.movScreen.Recording.2023-10-07.at.4.21.10.AM.movWhat alternative solutions did you explore? (Optional)We can also just remove |
📣 @Arcadekwizera! 📣
|
Contributor details |
✅ Contributor details stored successfully. Thank you for contributing to Expensify! |
Hello, How to join to Expensify group? |
📣 @corpitts! 📣
|
Contributor details |
|
Contributor details |
✅ Contributor details stored successfully. Thank you for contributing to Expensify! |
I can reproduce this on staging but not on the latest main. Can either of you still reproduce it on the latest main? |
📣 @abdel-h! 📣
|
@abdel-h66 I have, I can reproduce it easily on staging but have yet to reproduce it atall on main. |
Yes, I just checked on the latest main, and still could reproduce it. Try the reproduction steps on this comment #29038 (comment) |
@Ollyws Same here. It's easily reproducible. |
Ahh got it now, was a technical problem on my end. |
@abdel-h66 I like @allroundexperts proposal, it fixes the problem by using a common pattern we're already using in multiple places. 🎀👀🎀 C+ reviewed |
Triggered auto assignment to @mountiny, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
Yes I failed to mention in my comment the pattern seen ReportActionItemCreated which is how I got to my initial solution |
|
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.89-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2023-10-31. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
For reference, here are some details about the assignees on this issue:
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
@Ollyws could you please complete the BZ checklist here so we can prep to issue payment? |
BugZero Checklist:
https://github.com/Expensify/App/pull/23737/files#r1377413396
N/A
I don't think a regression test would be helpful here as it's fairly edge case, hard to test for accurately and doesn't affect the flow in any significant way. |
Great, TY! BZ checklist is now complete. |
All set to issue payment. @allroundexperts was assigned to the PR on 2023-10-09, and PR was merged on 2023-10-19, so no speed bonus is applicable here. This means we need to pay:
|
@Ollyws offer sent for $500! (Only $250 will be paid out because of regression). |
@ayazhussain79 offer for $50 sent! |
@allroundexperts could you please request $250 via NewDot and confirm here once complete? |
@joekaufmanexpensify offer accepted, Thank you |
We did have a regression from this one. |
Ah, okay. Thanks for flagging that! In that case, the 50% regression penalty applies here. I've adjusted the payment amounts above to reflect this. |
@Ollyws $250 sent and contract ended! |
@ayazhussain79 $50 sent and contract ended! |
Chatted with @allroundexperts and confirmed they already submitted a request here, so this is all set. |
Closing as we're good to go here. Payment summary message is here. Thanks everyone! |
$250 payment approved for @allroundexperts based on this comment. |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Action Performed:
Expected Result:
The page should smoothly scroll up and down without getting stuck
Actual Result:
Scrolling is not properly, and the page sometimes gets stuck when scrolling on the distance detail page
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.79-3
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
screen-recording-2023-10-04-at-113521-pm_daRS8ow5.mp4
Recording.16.mp4
Expensify/Expensify Issue URL:
Issue reported by: @ayazhussain79
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1696444461290349
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: