Skip to content
This repository has been archived by the owner on May 1, 2024. It is now read-only.

[Spec] Remove Experimental Flag from Drag and Drop Recognizers #11663

Closed
PureWeen opened this issue Aug 5, 2020 · 1 comment
Closed

[Spec] Remove Experimental Flag from Drag and Drop Recognizers #11663

PureWeen opened this issue Aug 5, 2020 · 1 comment
Labels
in-progress This issue has an associated pull request that may resolve it! proposal-open t/enhancement ➕
Milestone

Comments

@PureWeen
Copy link
Contributor

PureWeen commented Aug 5, 2020

Considerations before letting drag and drop leave experimental

The API is largely a copy paste from UWP

  • Does AllowDrag/CanDrop make sense as property names? Would Enabled make more sense? Should these be true by default? [x]
  • CollectionView implementation
  • Can users extend the drag and drop handlers at the platform level so provide customization. For example on iOS/uwp you can provide custom animations
  • Does the DataPackage make sense?
  • Drag Leave [x]
  • Fix accepted Operations [x]
@samhouts samhouts added this to New in Triage Aug 5, 2020
@PureWeen PureWeen moved this from New to Ready For Work in Triage Aug 5, 2020
@PureWeen PureWeen added this to the 5.0.0 milestone Aug 5, 2020
@samhouts samhouts moved this from Ready For Work to Needs Estimate in Triage Aug 6, 2020
@samhouts samhouts added this to To do in vNext+1 (5.0.0) Aug 11, 2020
@squinn7
Copy link

squinn7 commented Aug 14, 2020

Just took a look at it and it works great. Especially cool because I worked on a previous project where we hand spun this with renderers and it took a lot of effort.

As a suggestion, we used drag and drop to implement a planner app with calendars and timelines. Something that I can't figure out is if you can get the position of the drop on the screen from the event.

If this isn't in here I might suggest this as an important feature because it lays the ground work for easy implementation of an end user view manipulation feature.

@samhouts samhouts added the in-progress This issue has an associated pull request that may resolve it! label Aug 21, 2020
@samhouts samhouts moved this from To do to Done in vNext+1 (5.0.0) Aug 26, 2020
Triage automation moved this from Needs Estimate to Closed Aug 27, 2020
@PureWeen PureWeen reopened this Aug 27, 2020
Triage automation moved this from Closed to New Aug 27, 2020
vNext+1 (5.0.0) automation moved this from Done to To do Aug 27, 2020
@samhouts samhouts moved this from To do to Done in vNext+1 (5.0.0) Aug 27, 2020
@samhouts samhouts moved this from New to Ready For Work in Triage Aug 27, 2020
@samhouts samhouts moved this from Ready For Work to Needs Estimate in Triage Aug 27, 2020
@jfversluis jfversluis closed this as not planned Won't fix, can't repro, duplicate, stale Dec 7, 2023
Triage automation moved this from Needs Estimate to Closed Dec 7, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
in-progress This issue has an associated pull request that may resolve it! proposal-open t/enhancement ➕
Projects
Triage
  
Closed
Development

No branches or pull requests

4 participants