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
If I call setRequired with the parameter "false", setAllowBlank is also called with the value false instead of !required, resulting in a required value.
I can't see why validateOnBlur is called at all, nor why allowBlank is called with false.
The text was updated successfully, but these errors were encountered:
Yes, as soon as I call setRequired with the parameter false, blank value is not allowed anymore.
The explanation I wrote in my first message is still true: no matter what value is given to setRequired, the methods setValidateOnBlur and setAllowBlank are called, the first one with hard-coded parameter true, the second one with hard-coded parameter false, which disallow blank value.
gwt-material/gwt-material/src/main/java/gwt/material/design/client/base/mixin/RequiredFieldMixin.java
Line 55 in 580869f
If I call setRequired with the parameter "false", setAllowBlank is also called with the value false instead of !required, resulting in a required value.
I can't see why validateOnBlur is called at all, nor why allowBlank is called with false.
The text was updated successfully, but these errors were encountered: