-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
drag events dataTransfer is undefined in RC5 alpha 7-2 with NgModule imports #1025
Comments
+1 hammerjs is overriding the original drag events with no way to access the original event. |
Why are "drag", "dragstart" and "dragend" being created as custom events, when they are native events? https://github.com/angular/material2/blob/master/src/lib/core/gestures/MdGestureConfig.ts Unless I missed something I don't think "drag", "dragstart" or "dragend" are being used in any component yet. Thanks in advance :-) |
We removed |
Removes the `drag` event from the gesture config. Fixes angular#1025.
Removes the `drag` event from the gesture config. Fixes angular#1025.
Removes the `drag` event from the gesture config. Fixes angular#1025.
Removes the `drag` event from the gesture config. Fixes #1025.
Removes the `drag` event from the gesture config. Fixes angular#1025.
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Bug, feature request, or proposal:
Bug: Since adding in Md*Module(s) and hammerjs, drag events no longer contain the dataTransfer property.
This did not happen when directly using the Md* components in our components. Once we added the Md*Module(s) to NgModule and installed hammerjs this error arose.
What is the expected behavior?
drag events should have the dataTransfer property to be able to pass data in the dropped element
What is the current behavior?
error above
What are the steps to reproduce?
(I'm working on it, but can't figure out how to get ng2 rc5 and md alpha7-2 all in the same plunker...)
Plunker template: http://plnkr.co/edit/o077B6uEiiIgkC0S06dd
Which versions of Angular, Material, OS, browsers are affected?
Angular 2 RC5
Material alpha 7-2
hammerjs 2.0.8
Windows 8.1
Chrome and FF latest
Is there anything else we should know?
It's worth noting that this error occurs in a component with NO MD components in use. But it only happens if we NgModule import the MD components (needed elsewhere in the application). It doesn't make sense, but our draggable div isn't an md-* component! But if I remove them from NgModule imports I can drag it!
The text was updated successfully, but these errors were encountered: