The Floating Label Autocomplete demo is broken in versions 1.0.0, 1.0.1 and HEAD, although it was working in 0.11.4. Leaving the field empty does not cause the form to have the 'required' error.
Other validations (min, max) seem to be working.
Related to #6313.
@topherfangio Any one working on this?
It should work if you put required="true"
it looks like required="true" does work
Yes it does !
It is a small bug in the parsing of the required attribute.
I will do a merge request as soon as I can (tomorrow Paris time)
Thank you!
Ok great! Thanks
seems like required="true" makes sense but ng-messages still not working
i installed bower component "angular-material": "1.0.6"
but i feel the issue #6393 still exist.

@MasterRam The fix has been released in 1.1.0-rc1, not in v1.0.6
+1
Thanks It is working fine....:)
On Apr 3, 2016 6:54 AM, "kevinlbatchelor" [email protected] wrote:
+1
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
I am using angular material 1.1.1. I am not able to get my required autocomplete to work. The form does not submit, to the required attribute is working but the ng-message never shows.
Gist
I have tried all above suggestions ...
So after reviewing #1780 and @91K00 code it appears that the required only 'works' (meaning displays) when the <md-autocomplete> is wrapped with <md-input-container>, this does not match the documentation. I am also not a huge fan of the moving floating label. Can we fix the required to display when NOT using the <md-input-container> wrapper. Thanks
I'm observing the same exact issue as @jonathanread : In 1.1.1 the md-autocomplete does not work using 'md-required' or 'required' tags. This is inconsistent with other elements and the documentation.