To be more clear: the invalid style is applied to the input elements when the form is initially rendered and before the user has had a chance to enter data. My user's don't like this: it's too in your face but I don't see a way around this side effect if I continue to use an ng-invalid style.
On Tuesday, June 30, 2015 at 11:53:46 AM UTC-7, [email protected] wrote: > > Greetings, > > I'm a big fan of Angular and have been developing a real world app with it > for a few months now. One aspect that is tripping me up from a UX > perspective is using "ng-invalid" with input elements. Imagine we have a > form with a number of input elements which have no reasonable default > value. NG automatically adding a style of .ng-invalid results in all of > those inputs being styled as invalid. I am of the opinion that this is not > ideal and that empty elements should be considered valid and instead dealt > with using ng-required. I think this would result in cleaner code and > improved UX. That said, perhaps there is something I don't understand here > and I am hopeful someone can set me straight. > > Thank for your time! > > Ken > > > -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
