I have the strangest behaviour in Alfresco 2.9.
A custom property is defined as an int with a MINMAX constraint. It is also set to be read-only in the webclient configuration.
As an admin I can nevertheless edit it - I guess it comes with the rights of admin that read-only is not enforced in the webclient. And if I try to enter a value outside of the MINMAX range, the restriction is enforced and I can't. The error-message appears as text on the page, NOT as a pop-up. So far so good. Null-values seem to be allowed, again ok since the property is not explictly set to mandatory.
However when updating the property page in the webclient as a more restricted user than admin, I get a javascript pop-up message complaining that the null-value of the property, non-editable for this user, is outside of the MINMAX range. It doesn't make sense to me that a restriction on the model depends on the user entering the data. I also don't understand why one user sees a javascript-pop-up and the other doesn't.
****EDIT****
On closer inspection, the difference is not so much in the choice of user, but in the choice of button I push.
When choosing "Save" in the property-edit page, for both users the null-value is accepted.
When choosing "Continue" in the property-edit page, for both users the javascript pop-up appears.
****EDIT****
Any idea where this behavior is coming from?
