You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 12, 2024. It is now read-only.
Example here. Basically it doesn't add the intermediate classes when showing and hiding.
The workaround is pretty simple, just don't use ngView on the body. In the example if you move ngView down onto a div it works fine.
There are a few scattered issues on stackoverflow where it does say you get some odd behaviour when adding ngView to the body but most of them aren't serious. If we shouldn't be doing this, I think there should be a warning in the docs about it.
The text was updated successfully, but these errors were encountered:
matsko
added a commit
to matsko/angular.js
that referenced
this issue
Sep 17, 2015
Relying on the body node to be present right at injection has
caused issues with unit testing as well as some animations on
the body element. Reverting this patch fixes these issues.
Closesangular#12874
Prior to this fix anchoring would allow for a container to be a document
node or something higher beyond the body tag. This patch makes it fall
back to body incase the rootElement node exists as a parent ancestor.
Closesangular#12874
Relying on the body node to be present right at injection has
caused issues with unit testing as well as some animations on
the body element. Reverting this patch fixes these issues.
Closes#12874
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
http://plnkr.co/edit/PgfQaoDE5iCaxV2AX8OA
Example here. Basically it doesn't add the intermediate classes when showing and hiding.
The workaround is pretty simple, just don't use ngView on the body. In the example if you move ngView down onto a div it works fine.
There are a few scattered issues on stackoverflow where it does say you get some odd behaviour when adding ngView to the body but most of them aren't serious. If we shouldn't be doing this, I think there should be a warning in the docs about it.
The text was updated successfully, but these errors were encountered: