Clear trigger being visible when field is readOnly/disabled

[scebotari66]

Hello team!

The clearable field config API docs state the folowing:

Show a trigger to clear field, if this field is not readOnly. The trigger is available in the triggers object under the name clear.

Right now the clear trigger still shows up on readonly fields. It also appears on disabled fields. Neither of those should display the clear trigger.

Code sample: https://codepen.io/scebotari66/pen/MYyaJwr

[mats]

Confirmed - we'll get it fixed! https://github.com/bryntum/support/issues/12217

[scebotari66]

Thanks Mats!

Great to hear.

[scebotari66]

It is marked as fixed in 7.0.0, but actually it is not. Still reproducible.

[alex.l]

Hi,

Thank you for the report, reopened!

[Animal]

The fix implemented was

.b-field {
    &.b-read-only,&.b-disabled {
        .b-field-trigger {
            pointer-events : none;
            opacity        : .5;
        }
    }
}

So it made the tiggers less visible when disabled but not hidden. It is still valid information for a user to be able to "read" the UI.

If you want to make the clear trigger totally hidden when disabled or read-only, you can use CSS to do it:

.b-field {
    &.b-read-only,&.b-disabled {
        .b-field-trigger[data-ref="clear"] {
            display : none;
        }
    }
}

[johan.isaksson]

The discussion leading up to fading the triggers instead of fully hiding them was that it leads to a less jumpy UI for forms etc that disable / enable some fields based on others and similar use cases. Especially for triggers placed first in the fields.

The CSS suggested by Nige above will hide the triggers fully, but we are open to consider adding a config to control this behavior too - please let us know your thoughts on it