IE9 Unable to get value of the property 'nodeName': object is null or undefinedundefined

AngularJS application is loaded in via AJAX (Apache Wicket). Manually started and works fine in Chrome/FF.

Internet explorer gives the error "Unable to get value of the property 'nodeName': object is null or undefinedundefined" and stops.

[petebacondarwin]

Have you followed all the guidance in http://docs.angularjs.org/guide/ie?

On 9 July 2013 14:02, Maikel notifications@github.com wrote:

AngularJS application is loaded in via AJAX (Apache Wicket). Manually
started and works fine in Chrome/FF.

Internet explorer gives the error "Unable to get value of the property
'nodeName': object is null or undefinedundefined" and stops.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/3172
.

Yes

[pkozlowski-opensource]

@maikeldus I'm afraid that we will need a live reproduce scenario to move forward on this one. It is impossible to figure out what is going on here without the live reproduce scenario. Could you add one using plunker, jsfiddle or similar?

[pkozlowski-opensource]

@maikeldus we haven't heard from you so going to close this issue for now. Please do reopen it when you've got a reproduce scenario.

[nmccready]

I am having the same issue. I can provide the source as well.

Im sorry i did not awnser for 2 months. The issue was that the HTML markup was not correct in that certain document. IE has many strict(er) rules to comply (for example what tags you put in an table).

Instead of checking the source by a HTML validator, i checked the DOM HTML created by Internet Explorer (accesiable by the IE developer tools: F12). In this document i found two emtpy tags (<>) within a table which caused angular not to start. It turns out tags weren't appropriately closed.

[nmccready]

I figured mine out as well. Mine was caused to invalid dom elements inside a table element without 'td' . IE fails where Chrome,Firefox and others pass.