-
Notifications
You must be signed in to change notification settings - Fork 25.8k
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
TypeError: Cannot read property 'animate' of null #10230
Comments
Adding a short plunker would help us handle the issue quicker |
Sorry. It's hard to reproduce in a plunker. Also, it is a random issue. Once you refresh it goes away. But i found another issue #10191 which also points to the exact same problem. |
…node Closes angular#10230 Closes angular#10191 Closes angular#10273
…node Closes angular#10230 Closes angular#10191 Closes angular#10273
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. |
I'm submitting a ... (check one with "x")
Current behavior
I'm using Chrome 51 and Angular 2.rc4 and following errors popup in the console when loading my angular app.
Expected/desired behavior
This error should not show as i am not using animations explicitly and this does not happen on other browsers.
Reproduction of the problem
I do not have a plunker for this but i have a live site demo here. Visit this url in Chrom 51(or the latest) and you will see the error on first load. The second page load seems fine for some reason.
Here is the line causing error. Somehow, Chrome finds
document.body
to benull
.platform-browser.umd.js
Also, if it helps, i'm using systemjs-builder to bundle app files
Here is my systemjs config
And here is the app bootstrap
What is the expected behavior?
This error should not show as i am not using animations explicitly and this does not happen on other browsers.
What is the motivation / use case for changing the behavior?
I don't know how to answer this.
Please tell us about your environment:
The text was updated successfully, but these errors were encountered: