Uncaught TypeError: Cannot read the "ca" property from null when dragging a Google map

I have an Ionic 2 beta 7 application (also appears in beta 6) that uses the Google Maps JavaScript API.

If I click on a map, drag it and β€œdrop” the map before releasing the click, it causes this error the next time I try to drag the map.

Here is the JavaScript stack trace

TypeError: Cannot read the 'ca' property from null on .r.Kj ( https://maps.googleapis.com/maps-api-v3/api/js/25/7/common.js:215:70 ) in Object..B.trigger ( https://maps.googleapis.com/maps/api/js?key=MYKEY:93:119 ) at dy ( https://maps.googleapis.com/maps-api-v3/ api / js / 25/7 / common.js: 164: 140 ) c. ( https://maps.googleapis.com/maps-api-v3/api/js/25/7/common.js:163-00-0041 ) in Object._. B.trigger ( https://maps.googleapis.com/maps/api/js?key=MYKEY:93:119 ) on .r.dl ( https://maps.googleapis.com/maps-api-v3/ api / js / 25/7 / common.js: 228: 350 ) on Kv..r.fm ( https://maps.googleapis.com/maps-api-v3/api/js/25/7/common. js: 195: 106 ) in ZoneDelegate.invokeTask ( http: // localhost: 8100 / build / js / zone.js: 356: 38 ) in Zone.runTask ( http: // localhost: 8100 / build / js / zone. js: 256: 48 ) in ZoneTask.invoke ( http: // localhost: 8100 / build / js / zone.js: 423: 34 )

Although this does not seem to cause user interface problems from a user perspective, it would be nice to know if there is a way to prevent this?

Note

When dragging a card and freeing it when the mouse is static, this error does not occur the next time you drag it.

Plunger example

I created a Plunker example that replicates a problem. Follow these steps:

  • Open Developer Tools (F12)
  • Drag the map and click
  • Try dragging the map again.
  • The error is called and written to the console

Refresh

The trace and title of the question stack has been updated to match what was discovered in Ionic 2 beta 10

GitHub Track

This issue was raised on the ZoneJS GitHub page so you can track it here.

+5
source share
1 answer

To notify anyone who did not follow this issue on GitHub (the one I linked in this question), this bug was fixed in ZoneJS version v0.16.7

+1
source

All Articles