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
It's not possible to make fields not operational dynamically. Right now we achieve that using the visibility field but we prefer to inform users that if the enabled field is false then other fields are still there but are not operational.
It would be nice to have a feature allowing developers to disable a form field but not hide it. In this case when the field is disabled (for example) turnes gray, the value can't be changed, bu it's still displaying the latest value.
Reasons
In our case we want to allow users to edit fields gateway and host only when the enabled field is true. In other cases values for these fields should be displayed but not possible to edit/change them.
Description
It's not possible to make fields not operational dynamically. Right now we achieve that using the
visibility
field but we prefer to inform users that if theenabled
field is false then other fields are still there but are not operational.It would be nice to have a feature allowing developers to disable a form field but not hide it. In this case when the field is disabled (for example) turnes gray, the value can't be changed, bu it's still displaying the latest value.
Reasons
In our case we want to allow users to edit fields
gateway
andhost
only when theenabled
field is true. In other cases values for these fields should be displayed but not possible to edit/change them.Our module allows both configurations:
and
so we should not hide the
gateway
and thehost
in the form view when theenabled
field is falseAttachments
Our solution is described here
The text was updated successfully, but these errors were encountered: