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 has been archived by the owner on Sep 5, 2024. It is now read-only.
Try and push the submit button in this CodePen and see that the message is set into DOM but its opacity is 0.
It will need something along the lines of:
form.ng-submitted [ng-messages] {
opacity:1;
}
The text was updated successfully, but these errors were encountered:
chr22
changed the title
RC4: ng-messages isn't shown when submitted
RC4: ng-messages isn't shown when form is submitted, but input is untouched
Nov 16, 2015
The behaviour of showing the error messages changed silently: Compare the "Errors" section on 0.11.4 with 1.0.0-rc4.
Now it seems to be aligned with the attribute description of the md-is-error attribute on the md-input-container API page.
However there has not been any hint in the changelog. This was discussed several times I think, so is this an Issue or a fix?
Added check for parent form `$submitted` attribute.
Notice that `novalidate` attribute should be applied on parent form in order to make it work (Browser preventing submit when not specified)
fixes#5752
Added check for parent form `$submitted` attribute.
Notice that `novalidate` attribute should be applied on parent form in order to make it work (Browser preventing submit when not specified)
fixes#5752
Try and push the submit button in this CodePen and see that the message is set into DOM but its opacity is 0.
It will need something along the lines of:
The text was updated successfully, but these errors were encountered: