-
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 2024-05-22] [$250] Submit expense - Floating 'Lets go' Above Upload Recipient Statement When Dragging and Dropping Files #40897
Comments
Triggered auto assignment to @alexpensify ( |
We think that this bug might be related to #vip-split |
@alexpensify FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors. |
ProposalPlease re-state the problem that we are trying to solve in this issue.The intruction text is still visible when dragging over a file on a manual add receipt page. What is the root cause of that problem?We get the dragging state from the drag and drop context,
and hide the instruction text if we are dragging over a file.
This works for scan page in the first/start page because we wrap it with DragAndDropProvider. App/src/pages/iou/request/IOURequestStartPage.tsx Lines 132 to 148 in 9cceec8
However, if we open the scan page from the Add receipt menu, the IOURequestStepScan isn't wrapped with a drag and drop provider, so getting the context will result in undefined value. What changes do you think we should make in order to solve the problem?We can expose the dragging state from
or we can fully use App/src/pages/iou/request/step/StepScreenDragAndDropWrapper.tsx Lines 32 to 34 in b0ec7b1
What alternative solutions did you explore? (Optional)Create a wrapper component that will wrap IOURequestStepScan with the drag and drop provider. |
This one is on my testing list, I should have an update soon. |
No update yet, I've been focused on other GHs. |
@alexpensify you need to access the scan page from the manual confirmation page here (Add receipt) The issue doesn't happen on the scan start page, but happens if you access it from the confirmation page |
Heads up, I will be offline until Tuesday, May 7, 2024, and will not actively watch over this GitHub during that period.If anything urgent is needed here, please ask for help in the #expensify-open-source Slack Room-- thanks! I will test this one more when I get back online. |
Thanks for clarifying this step:
|
Job added to Upwork: https://www.upwork.com/jobs/~01316df55587475e87 |
Triggered auto assignment to @miljakljajic ( |
Heads up, I will be offline until Tuesday, May 28, 2024, and will not actively watch over this GitHub during that period.@miljakljajic - While I'm offline, I need help here completing the payment process after this one clears the 7-day period on 2024-05-22. Thanks! |
@bernhardoj has been hired on the upwork job. @mollfpr do we pay you via manual request, or in upwork? |
@miljakljajic I'll do a manual request, could you help with the payment summary? I'll finish the checklist ASAP. Thank you! |
Of course. @mollfpr is owed 250 USD for their work reviewing this PR. |
No offending PR was found.
The regression step should be enough.
Only the web/desktop can drag a file |
I'm back online and taking over as the BZ member here. Tomorrow, I'll create the regression test GH based on today's update. |
Closing - The QA request has been created for this one. Thanks! |
$250 approved for @mollfpr |
@miljakljajic this payment will end up going through New Expensify. I've closed out the Upwork job since payment wasn't issued. Do you mind adding a payment summary for @bernhardoj? |
Of course! @bernhardoj is owed 250 USD for their work reviewing this issue. |
$250 approved for @bernhardoj |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: v1.4.65-2
Reproducible in staging?: y
Reproducible in production?: y
Issue reported by: Applause - Internal Team
Action Performed:
Expected Result:
When dragging and dropping files onto the recipient area, the "Let's Go" prompt should not float above the upload recipient statement. Instead, the upload recipient statement should be replaced by "Let's Go," similar to the behavior in the scan section.
Actual Result:
The "Lets go" text floats above the upload recipient statement when dragging and dropping the file onto the recipient. this causes inconsistency with Scan section.
Workaround:
n/a
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6460213_1713961786371.Screen_Recording_2024-04-24_at_5.16.47_AM.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @miljakljajicThe text was updated successfully, but these errors were encountered: