Disabled Conditions for Fields

[ryanleichty]

We use the Visibility Conditions quite a bit to hide/show fields based on other selections. Often times, this is exactly what we want. But other times, this can feel a bit jarring when multiple things hide/show based on a selection. It might be helpful to instead have the option to disable the field so that it's still visible.

I'm not sure if it makes sense within the Editability Conditions since the desired outcome is that the field appears disabled (with no active selection). A new Disabled Conditions section?

[thupsi]

Good idea! I too think it's sometimes jarring when multiple fields hide/show based on a selection.

[brandonkelly]

Not sure I’m following. This is exactly what the Editability Conditions are for.

[brandonkelly]

If I understand correctly, one difference here is the "Entry Condition" within the Editability Conditions group, which I agree would be nice to have.

What do you mean by that? Both Visibility Conditions and Editability Conditions have an Entry Condition within them.

Currently, you can't really tell that a field is disabled (e.g., currently the background theme field is disabled). All you see is the disabled cursor on hover.

Yeah that makes sense – disabled fields should be more visually distinct when placed alongside other fields that are editable.

[ryanleichty]

This is all that I see:

We're currently on Craft 5.8.19

[brandonkelly]

Doh… sorry. I saw both in your screenshot above and didn’t realize that was a mockup.

[brandonkelly]

Added the element-based condition for 5.9 (3f5ba50). We’ll discuss the styling in our next team call.

[ryanleichty]

My bad! I should've noted that was just a mockup. Thank you! 🔥