You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[HOLD for payment 2023-08-08] [$1000] Web - The Not Allowed sign is not shown when dragging & dropping attachments if the settings or search bar is open #22305
Notice that the Not Allowed sign is not shown and when you drop it, the attachment is opened in a new tab.
Expected Result:
Not allowed sign is not shown
Actual Result:
Not allowed sign is shown
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Android / native
Android / Chrome
iOS / native
iOS / Safari
MacOS / Chrome / Safari
MacOS / Desktop
Version Number: 1.3.36-4 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
Create a NoDropZone component( this will just render the children passed as Prop. and apply dragover eventListner with
e.datatransfer.dropeffect = "none"
only on web we apply the eventListner. on Native it will render the children only similar to what we have Done with DropZone component.
What alternative solutions did you explore? (Optional)
we can add a eventlistner for both dragover and drop and event.preventDefault() on both listners it fails the drop gracefully(no new Tab opens) but the native cursor style for drop not-allowed (🚫 with white box) of windows, it still shows +Copy which indicates user can drop the file.
changed the title [-]Web - The Not Allowed sign is not shown when dragging & dropping attachments if the settings or search bar is open[/-][+][$1000] Web - The Not Allowed sign is not shown when dragging & dropping attachments if the settings or search bar is open[/+]on Jul 11, 2023
Assuming no other regressions arise, we should process payments as follows:
[ ] Bug reporter @daveSeife $250
[ ] Contributor @ishpaul777 $500 (50% docking on original price due to regression)
(there is no C+ payment since RobertK is with SWM agency 👍 )
I'll take this over when I return if it's not complete. Thanks in advance @sakluger
I went ahead and paid @daveSeife for the bug report today. Tomorrow is the payment date for the rest assuming no more issues arise.
@robertKozik could you please complete the BugZero checklist (GH comment) when you have some time so that we can close this issue out after payment? Thanks!
@sakluger I'm not sure whether I filled it right, as this issue was not fixing any regression (only caused one 🥲). Ping me if it should be filled another way
[@robertKozik] The PR that introduced the bug has been identified. Link to the PR: This PR was not fixing the regression
[@robertKozik] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment: N/A
[@robertKozik] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion: N/A
[@robertKozik] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
So you're right about it not being a regression, I believe. For the regression test, we might want to add one though - basically the testing steps in this issue. Thanks!
Activity
melvin-bot commentedon Jul 5, 2023
Triggered auto assignment to @michaelhaxhiu (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.melvin-bot commentedon Jul 5, 2023
Bug0 Triage Checklist (Main S/O)
Platformsin OP are ✅)ishpaul777 commentedon Jul 8, 2023
Proposal
Please re-state the problem that we are trying to solve in this issue.
Web - The Not Allowed sign is not shown when dragging & dropping attachments if the settings or search bar is open
What is the root cause of that problem?
The current behaviour of dragover event datatransfer dropeffect is "copy" on setting screens.
What changes do you think we should make in order to solve the problem?
We need to add a eventlistner for dragover and set e.datatransfer.dropeffect = "none" in callback function when the right sidebar renders
Ref- https://codepen.io/SitePoint/pen/epQPNP
Here is What we need to do:
e.datatransfer.dropeffect = "none"
only on web we apply the eventListner. on Native it will render the children only similar to what we have Done with DropZone component.
Result-
https://www.loom.com/share/301ba3610bc845fda18b3c0fa977335b?sid=39f313e6-45e8-41a8-9ede-9fa251cd3a0e
What alternative solutions did you explore? (Optional)
we can add a eventlistner for both dragover and drop and event.preventDefault() on both listners it fails the drop gracefully(no new Tab opens) but the native cursor style for drop not-allowed (🚫 with white box) of windows, it still shows
+Copywhich indicates user can drop the file.melvin-bot commentedon Jul 11, 2023
@michaelhaxhiu Huh... This is 4 days overdue. Who can take care of this?
[-]Web - The Not Allowed sign is not shown when dragging & dropping attachments if the settings or search bar is open[/-][+][$1000] Web - The Not Allowed sign is not shown when dragging & dropping attachments if the settings or search bar is open[/+]melvin-bot commentedon Jul 11, 2023
Job added to Upwork: https://www.upwork.com/jobs/~010c9a4080884f501d
melvin-bot commentedon Jul 11, 2023
Current assignee @michaelhaxhiu is eligible for the External assigner, not assigning anyone new.
melvin-bot commentedon Jul 11, 2023
Triggered auto assignment to Contributor-plus team member for initial proposal review - @Santhosh-Sellavel (
External)75 remaining items
michaelhaxhiu commentedon Aug 4, 2023
Note: I'm preparing to go OOO for ~2 weeks and need a BZ buddy to watch over this in the meantime. 🙏
Next steps:
[ ] Bug reporter @daveSeife $250
[ ] Contributor @ishpaul777 $500 (50% docking on original price due to regression)
(there is no C+ payment since RobertK is with SWM agency 👍 )
I'll take this over when I return if it's not complete. Thanks in advance @sakluger
ishpaul777 commentedon Aug 4, 2023
@michaelhaxhiu according to guidelines, isn't it just dock the speed bonus because of regression, i couldn't find the penalty for regression in docs
michaelhaxhiu commentedon Aug 4, 2023
https://github.com/Expensify/App/blob/main/contributingGuides/CONTRIBUTING.md#payment-for-contributions
ishpaul777 commentedon Aug 4, 2023
found it! I beleive this is added recently so i missed it! Thanks @michaelhaxhiu
sakluger commentedon Aug 7, 2023
I went ahead and paid @daveSeife for the bug report today. Tomorrow is the payment date for the rest assuming no more issues arise.
@robertKozik could you please complete the BugZero checklist (GH comment) when you have some time so that we can close this issue out after payment? Thanks!
daveSeife commentedon Aug 8, 2023
@sakluger I have received the payment, thank you!
robertKozik commentedon Aug 8, 2023
@sakluger I'm not sure whether I filled it right, as this issue was not fixing any regression (only caused one 🥲). Ping me if it should be filled another way
Edited
dangrous commentedon Aug 8, 2023
So you're right about it not being a regression, I believe. For the regression test, we might want to add one though - basically the testing steps in this issue. Thanks!
ishpaul777 commentedon Aug 9, 2023
Bump @sakluger for pay reminder. Thanks!
sakluger commentedon Aug 9, 2023
Completed payment including 50% penalty for the regression.
@robertKozik thanks for filling out the checklist and writing out regression steps, looks perfect!