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 Sep 5, 2024. It is now read-only.
Repository navigation
This repository was archived by the owner on Sep 5, 2024. It is now read-only.
@EladBezalel Yes actually it is related to the styes. But updating the style selectors won't be the right solution, because the ngMessage isn't retrieving the animation class correctly.
This is caused by the parent transclusion from the autocomplete.
Pull request #5637 removed the code the replaces a wrapper div generated by mdAutocomplete. See this line: 05d7f24#diff-f700fe0b273e851967e22440f2c464eeL25
Also, see the occurences of the string md-autocomplete-replace in the whole repository. It was used as a marker class on the div to remove, but it is never taken into account.
Since mdInputContainer requires ngMessages to be a direct child, this might be the cause of the problem.
Activity
devversion commentedon Mar 9, 2016
Great demo, I'll take a look at this soon.
devversion commentedon Mar 18, 2016
Just investigated a bit and it seems to relate to the scope transclusion.
I tried to create a scope transclusion myself to take a look at its most elegant solution.
http://codepen.io/DevVersion/pen/WwRqaO?editors=1010
So just want to notify you, that this issue is in progress.
EladBezalel commentedon Mar 19, 2016
This is related to the styles applied,
Take a look at input messages style
devversion commentedon Mar 20, 2016
@EladBezalel Yes actually it is related to the styes. But updating the style selectors won't be the right solution, because the ngMessage isn't retrieving the animation class correctly.
This is caused by the parent transclusion from the autocomplete.
(https://github.com/angular/material/blob/master/src/components/input/input.js#L711)
EladBezalel commentedon Mar 20, 2016
👍
cairomassimo commentedon Apr 26, 2016
I am not sure if this may helps:
Pull request #5637 removed the code the replaces a wrapper div generated by mdAutocomplete. See this line:
05d7f24#diff-f700fe0b273e851967e22440f2c464eeL25
Also, see the occurences of the string
md-autocomplete-replacein the whole repository. It was used as a marker class on the div to remove, but it is never taken into account.Since
mdInputContainerrequiresngMessagesto be a direct child, this might be the cause of the problem.fix(input): add support for dynamically loaded ngMessage directives.
fix(input): add support for dynamically loaded ngMessage directives.
fix(input): add support for dynamically loaded ngMessage directives.
fix(input): add support for dynamically loaded ngMessage directives.
fix(input): add support for dynamically loaded ngMessage directives.