This repository has been archived by the owner on Sep 5, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
select(multiple): adding one resets pristine to true #6556
Labels
Milestone
Comments
devversion
added a commit
to devversion/material
that referenced
this issue
Jan 20, 2016
… is predefined. Bug introduced in 09bd5a3 Fixes angular#6556
devversion
added a commit
to devversion/material
that referenced
this issue
Jan 30, 2016
… is predefined. Bug introduced in 09bd5a3 Fixes angular#6556
ErinCoughlan
pushed a commit
to ErinCoughlan/material
that referenced
this issue
Feb 9, 2016
… is predefined. Bug introduced in 09bd5a3 Fixes angular#6556 Closes angular#6782 #breaking
I'm a bit confused on this, the commit which keeps being referenced as a fix is actually the cause of the issue, it attempts to fix the issue by causing a side effect on the form. It tries to mitigate the side effect by making a bad assumption that adding to a form with a value set at creation means the form should be clean. Which maybe a 50%+ case for uses but I think there is a very large gap of use cases which this is very bad. |
Splaktar
changed the title
Multiple md-select , adding one resets pristine to true
select(multiple): adding one resets pristine to true
Oct 25, 2018
Splaktar
added
resolution: fixed
severity: regression
This issue is related to a regression
labels
Oct 25, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
Ok this is my first message here.
Using lastest version of angularjs/material , it seems i found out an issue using md-select.
See this jsfiddle : http://jsfiddle.net/ypjgdzxp/3/
What you can see here is that i'm adding rows on the fly wich contains an md-select. The problem is that adding a new md-select to the Dom resets the form pristine to true , even if it was false/dirty before.
In my exemple , juste put anything in the upper input "Nom de couche" wich will make the form dirty , then add a new row using the "+" button at the bottom.
The text was updated successfully, but these errors were encountered: