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

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

Closed
coli opened this Issue Jun 15, 2012 · 1 comment

Comments

Projects
None yet
2 participants
@coli

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

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost 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.

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 join this conversation on GitHub. Already have an account? Sign in to comment