[ ] Checked the logs and have uploaded a log file and provided a link because I found something suspicious there. Please do not post the log file in the topic because very often something important is missing.
I’m submitting a…
[ ] Regression (a behavior that stopped working in a new release)
[x ] Bug report
[ ] Performance issue
[ ] Documentation issue or request
Current behavior
By enabling a workflow for making all fields disabled in a form (field canUpdate=false in workflow), when the schema content item is published, all the fields become disabled, except the x button of the fields, but that should be disabled as well.
The x button seems to only be disabled when the field is empty, irrespective of the state of the field (enabled or disabled).
Expected behavior
The x button (clear field) should be disabled when a field is disabled.
I just tried this on almost latest version (
Upgrade backend. (#885) 7c1b33961921fa8f2888a529edc9b67f57583424) and I am seeing the same behaviour. It is only when the workflow is using the ‘Prevent updates’ functionality causing the fields to appear disabled:
You can also see the faint ‘Disabled’ hint that you do not see when disabling with the workflow.
This obviously isn’t a massive issue as we cannot actually save these changes to disabled fields as the save button doesn’t exist, but it might cause a bit of confusion for our users.
