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
bug([dragAndDrop]): [Error when using drag and drop on mobile with firefox] #19385
Labels
P3
An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
Comments
jm06487
changed the title
bug([dragAndDrop]): [TITLE]
bug([dragAndDrop]): [Error when using drag and drop on mobile with firefox]
May 18, 2020
I noticed that this error only occurs when the touch simulation is enabled. When I turn it off it works as expected. |
crisbeto
added
has pr
P3
An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
and removed
needs triage
This issue needs to be triaged by the team
labels
May 19, 2020
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
May 19, 2020
The events that Firefox emits when it emulates a mobile device in the dev tools are incomplete which causes an error to be thrown at the end of a drag seequence. These changes add a bit of extra logic so everything doesn't break down. Fixes angular#19385.
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
May 19, 2020
The events that Firefox emits when it emulates a mobile device in the dev tools are incomplete which causes an error to be thrown at the end of a drag seequence. These changes add a bit of extra logic so everything doesn't break down. Fixes angular#19385.
jelbourn
pushed a commit
that referenced
this issue
May 21, 2020
The events that Firefox emits when it emulates a mobile device in the dev tools are incomplete which causes an error to be thrown at the end of a drag seequence. These changes add a bit of extra logic so everything doesn't break down. Fixes #19385.
jelbourn
pushed a commit
that referenced
this issue
May 21, 2020
The events that Firefox emits when it emulates a mobile device in the dev tools are incomplete which causes an error to be thrown at the end of a drag seequence. These changes add a bit of extra logic so everything doesn't break down. Fixes #19385.
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
P3
An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
Reproduction
Use StackBlitz to reproduce your issue: https://stackblitz.com/fork/components-issue
https://rllrpndgxxyy.angular.stackblitz.io/
Steps to reproduce:
1.
2.
Expected Behavior
What behavior were you expecting to see?
normal behavior.
Actual Behavior
What behavior did you actually see?
Error when on the drop.
Unhandled Promise rejection: point is undefined ; Zone: ; Task: Promise.then ; Value: TypeError: "point is undefined"
cdk 9.2.1/bundles/cdk-drag-drop.umd.js:872
cdk 9.2.1/bundles/cdk-drag-drop.umd.js:686
js 0.10.3/dist/zone.js:386
core 9.1.7/bundles/core.umd.js:28271
js 0.10.3/dist/zone.js:385
js 0.10.3/dist/zone.js:143
core 9.1.7/bundles/core.umd.js:28166
cdk 9.2.1/bundles/cdk-drag-drop.umd.js:683
cdk 9.2.1/bundles/cdk-drag-drop.umd.js:556
js 0.10.3/dist/zone.js:386
js 0.10.3/dist/zone.js:143
js 0.10.3/dist/zone.js:891
js 0.10.3/dist/zone.js:421
js 0.10.3/dist/zone.js:188
js 0.10.3/dist/zone.js:601
js 0.10.3/dist/zone.js:507
js 0.10.3/dist/zone.js:1671
js 0.10.3/dist/zone.js:1697
DragRef.prototype._getPointerPositionOnPage@https://rllrpndgxxyy.angular.stackblitz.io/turbo_modules/@angular/cdk@9.2.1/bundles/cdk-drag-drop.umd.js:872:17
DragRef.prototype._cleanupDragArtifacts/<@https://rllrpndgxxyy.angular.stackblitz.io/turbo_modules/@angular/cdk@9.2.1/bundles/cdk-drag-drop.umd.js:686:45
ZoneDelegate.prototype.invoke@https://rllrpndgxxyy.angular.stackblitz.io/turbo_modules/zone.js@0.10.3/dist/zone.js:386:30
onInvoke@https://rllrpndgxxyy.angular.stackblitz.io/turbo_modules/@angular/core@9.1.7/bundles/core.umd.js:28271:37
ZoneDelegate.prototype.invoke@https://rllrpndgxxyy.angular.stackblitz.io/turbo_modules/zone.js@0.10.3/dist/zone.js:385:36
Zone.prototype.run@https://rllrpndgxxyy.angular.stackblitz.io/turbo_modules/zone.js@0.10.3/dist/zone.js:143:47
NgZone.prototype.run@https://rllrpndgxxyy.angular.stackblitz.io/turbo_modules/@angular/core@9.1.7/bundles/core.umd.js:28166:32
DragRef.prototype._cleanupDragArtifacts@https://rllrpndgxxyy.angular.stackblitz.io/turbo_modules/@angular/cdk@9.2.1/bundles/cdk-drag-drop.umd.js:683:26
DragRef.prototype._endDragSequence/<@https://rllrpndgxxyy.angular.stackblitz.io/turbo_modules/@angular/cdk@9.2.1/bundles/cdk-drag-drop.umd.js:556:27
ZoneDelegate.prototype.invoke@https://rllrpndgxxyy.angular.stackblitz.io/turbo_modules/zone.js@0.10.3/dist/zone.js:386:30
Zone.prototype.run@https://rllrpndgxxyy.angular.stackblitz.io/turbo_modules/zone.js@0.10.3/dist/zone.js:143:47
scheduleResolveOrReject/<@https://rllrpndgxxyy.angular.stackblitz.io/turbo_modules/zone.js@0.10.3/dist/zone.js:891:38
ZoneDelegate.prototype.invokeTask@https://rllrpndgxxyy.angular.stackblitz.io/turbo_modules/zone.js@0.10.3/dist/zone.js:421:35
Zone.prototype.runTask@https://rllrpndgxxyy.angular.stackblitz.io/turbo_modules/zone.js@0.10.3/dist/zone.js:188:51
drainMicroTaskQueue@https://rllrpndgxxyy.angular.stackblitz.io/turbo_modules/zone.js@0.10.3/dist/zone.js:601:39
ZoneTask.invokeTask@https://rllrpndgxxyy.angular.stackblitz.io/turbo_modules/zone.js@0.10.3/dist/zone.js:507:25
invokeTask@https://rllrpndgxxyy.angular.stackblitz.io/turbo_modules/zone.js@0.10.3/dist/zone.js:1671:18
globalZoneAwareCallback@https://rllrpndgxxyy.angular.stackblitz.io/turbo_modules/zone.js@0.10.3/dist/zone.js:1697:31
zone.js:690:29
Environment
The text was updated successfully, but these errors were encountered: