Skip to content

Not Allowed sign is not shown when dragging attachments on LHN #23969

Closed

Description

@kavimuru

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:

  1. Open any chat
  2. drag attachments on LHN

Expected Result:

Not Allowed sign is shown when dragging the attachment on LHN

Actual Result:

Copy sign is shown when dragging the attachment on LHN

Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

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.48-0
Reproducible in staging?: y
Reproducible in production?: n
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

Test95.Dragonlhn-1.mp4

Untitled

Expensify/Expensify Issue URL:
Issue reported by: @daveSeife
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1690836365230309

View all open jobs on GitHub

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Jul 31, 2023
  2. melvin-bot commented on Jul 31, 2023

    @melvin-bot

    Triggered auto assignment to @dylanexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

  3. melvin-bot commented on Jul 31, 2023

    @melvin-bot

    Bug0 Triage Checklist (Main S/O)

    • This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
    • This bug is not a duplicate report (check E/App issues and #expensify-bugs)
      • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
    • This bug is reproducible using the reproduction steps in the OP. S/O
      • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
      • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
    • This issue is filled out as thoroughly and clearly as possible
      • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
    • I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync
  4. OSBotify commented on Jul 31, 2023

    @OSBotify
    Contributor

    👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open StagingDeployCash deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  5. melvin-bot commented on Jul 31, 2023

    @melvin-bot

    Triggered auto assignment to @marcaaron (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

  6. marcaaron commented on Jul 31, 2023

    @marcaaron
    Contributor

    @roryabraham do you maybe know what is up with this one? I thought I remember you saying something about refactoring drag and drop things.

  7. marcaaron commented on Jul 31, 2023

    @marcaaron
    Contributor

    Related PR -> #23589

  8. dummy-1111 commented on Aug 1, 2023

    @dummy-1111
    Contributor

    Proposal

    Please re-state the problem that we are trying to solve in this issue.

    Not allowed sign isn't shown when dragging attachment on LHN

    What is the root cause of that problem?

    We're not wrapping the LHN with NoDropZone

    What changes do you think we should make in order to solve the problem?

    Wrapping the SidebarLinks with NoDropZone would solve the issue

    1. Add fullScreen props with default true to the NoDropZone component
    2. Wrap the LHN with NoDropZone in SidebarLink.js with fullScreen={false}

    This works as expected

    Result

    What alternative solutions did you explore? (Optional)

  9. roryabraham commented on Aug 1, 2023

    @roryabraham
    Contributor

    We're not wrapping the LHN with NoDropZone

    @s-alves10 I don't think that's the root cause of the problem – its a proposed solution.

  10. dummy-1111 commented on Aug 1, 2023

    @dummy-1111
    Contributor

    @roryabraham

    Can you provide me with the link?

  11. roryabraham commented on Aug 1, 2023

    @roryabraham
    Contributor

    @marcaaron I'll grab this from you since I almost certainly caused it with #23589

  12. ginsuma commented on Aug 1, 2023

    @ginsuma
    Contributor

    I think it will be handled here #22218 (comment).

  13. allroundexperts commented on Aug 1, 2023

    @allroundexperts
    Contributor

    @roryabraham This is not a regression I think. LHN wasn't showing the not allowed icon before your PR as well.

  14. roryabraham commented on Aug 1, 2023

    @roryabraham
    Contributor

    I think it is a regression, because it's reproducible on staging but not main

  15. allroundexperts commented on Aug 1, 2023

    @allroundexperts
    Contributor

    Take a look at #22218. I think we're trying to use a different approach by disabling drag and drop entirely across the app and just enabling it for composer. We might want to combine these two issues.

  16. roryabraham commented on Aug 1, 2023

    @roryabraham
    Contributor

    Ok, going to close this one in favor of #22218 then and remove the deploy blocker

  17. roryabraham commented on Aug 1, 2023

    @roryabraham
    Contributor

    FWIW I think the simplest quick-and-dirty fix to this issue would be to update this listener to also set dropEffect: none on the event.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2Engineering

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions