This repository has been archived by the owner on Sep 5, 2024. It is now read-only.
md-subheader loses ng-if child elements when becoming sticky on Chrome #8500
Assignees
Labels
has: Pull Request
A PR has been created to address this issue
needs: investigation
The cause of this issue is not well understood and needs to be investigated by the team or community
Comments
devversion
added
the
needs: investigation
devversion
added a commit
to devversion/material
that referenced
this issue
May 19, 2016
* Currently the subheader was not working properly with `ng-if`'s inside of its content. This was caused by a wrong recompile of the already compiled transcluded clone. * This commit also fixes the meaningless / useless tests. Before we never imported the `subheader` module into its tests. Also we never tested the $mdSticky service together with the subheader, because we had a really ugly mock for the `$mdSticky` service, which just tested the call arguments. Fixes angular#8500. Closes angular#8504.
devversion
added
the
has: Pull Request
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Actual behavior:
Using an
md-subheaderwhich contains elements dynamically hidden or shown usingng-if, the dynamic elements vanish when the header becomes sticky. It appears the sticky clone of the header does not evaluate and/or update its content. This is reproducible in Chrome, though in Safari it works as expected.CodePen:
http://codepen.io/anon/pen/ONeMrm?editors=1000
Angular Versions:
Additional Information:
The text was updated successfully, but these errors were encountered: