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

Uncaught TypeError: Cannot read property 'nodeName' of undefined angular.js:5356 #1058

Closed
coli opened this issue Jun 15, 2012 · 1 comment · Fixed by #1062
Closed

Uncaught TypeError: Cannot read property 'nodeName' of undefined angular.js:5356 #1058

coli opened this issue Jun 15, 2012 · 1 comment · Fixed by #1062

Comments

@coli
Copy link

coli commented Jun 15, 2012

This bug is triggered when say a ng-click removes the node from the dom and you use $location service

Click on the button at http://jsfiddle.net/ADukg/258/

Uncaught TypeError: Cannot read property 'nodeName' of undefined angular.js:5356
(anonymous function) angular.js:5356
f.event.dispatch jquery.min.js:3
f.event.add.h.handle.i

This was working fine in say rc12 http://jsfiddle.net/ADukg/259/

@ghost
Copy link

ghost commented Jun 15, 2012

I am having a similar issue with 1.0.

http://jsfiddle.net/icub3d/daSJ5/4/

It looks like it's searching for an element to grab the href. Not sure why it needs to do that, especially when the ng-click is calling a function that uses $location.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants