I was made aware that if you create a new member-type which uses the umbraco.dropdown.flexible, as a mandatory property, then you would be able to save this new member without selecting anything from the dropdown.
Here is what is happening: if anything hasn't been picked then it would save the member with an empty string in the dropdown property. This would satisfy the property, as it technically has a value saved on the member.
Version of Umbraco: 7.12.3
Browser: Chrome, Firefox and Internet Edge.
Images:


I would have expected that it gave me a validation error as the user who created the member has not picked anything in the dropdown property.
It saved the member just fine.
There is no error messages that popups to help identify what is going on.
Bad news. This is a problem on documents as well. I'm looking into it now.
I've recreated this in both Members and Content docs.
I can see how to fix this for simple, single selections. The angular attribute ng-required="model.validation.mandatory" is missing.
Putting this in Umbraco.Web.UI.Client\src\views\propertyeditors\dropdownFlexible\dropdownFlexible.html to fixes it for both members and content but not for the multi-select (there is a switch for this but adding this attribute is ignored here).
It seems that this flexible was created under https://github.com/umbraco/Umbraco-CMS/pull/2502 so there is a dropdown and dropdownflexible.. guessing it's to support legacy. Not sure if to put this attribute on both?!
@cheeseytoastie you're right 馃槃 check the PR in #3504.
Doh! Wish I'd spotted that. I've just tested your changes and they work a treat for this issue.