-
Notifications
You must be signed in to change notification settings - Fork 3.4k
required attribute on md-select not working anymore #7067
Comments
@wembernard Thanks for filing a new issue. I will take a look. |
@wembernard
So I'm not sure if I really should implement the new parses for these type of attributes. |
@devversion ng-required didn't work either. Here is a Demo |
@wembernard In general |
@wembernard As native components (like |
Thanks @devversion for looking into this. The form from being submitted is indeed one of my problems. I guess whether it's a simple input or a complex md-select, submitting forms should behave the same way: either block the submission or send it. I'm ok using The second one is the display: it should be red to inform user one of the validation on this field did not pass. Just like a simple , right? |
@wembernard Yes definitely, it should be red. Extra for this case was |
@devversion I added the simple input to note behaviour differences: http://codepen.io/anon/pen/qbLJvV?editors=1010 |
@wembernard Yes, I know, the native input with |
@wembernard I'll close that issue because the attribute in general works. (required
About the form validation (errors when submitting form) there was already an issue, but this was focused on the |
@devversion The codepen.io you linked specifically indicates how md-select does not work with The cdn in that codepen is no longer valid, I used 1.0.9 version cdn, maybe the bug was introduced between versions 1.0.5 and 1.0.9. |
@bpaczkowski I've updated the codepen assets to use The codepens show clearly how the select integrates the
The form will be always submitted, regardless of the select, because you explicitly click on the submit button and the browser can't detect the There is nothing we can do about native submit prevention. |
Ahh, so that's the reason why it was still submitting. Thank you for clarifying this for me. |
Issue Fixed in version 1.13 #8529 |
|
I guess it's related to #6393 but @devversion didn't seem to fix md-select (only md-autocomplete), so I'm opening a new issue.
I've been trying
with angular-material#1.0.3 and angular-material#1.0.5 but didn't make it work.
Some Demo
Any idea/news on this problem?
The text was updated successfully, but these errors were encountered: