Extend the behavior of the Chips to allow "readonly" state

[carlosgarciaibanez]

Goal

We want to be able to set a "readonly" status for the Chip components so that we can disable all user interactions on them on specific scenarios (for example, when some data loading is in progress and we don't want the user to trigger a new request from the chips in the meantime).

Context

During the integration tests for the Conversational Search developed for Movistar ES an issue was detected (O2UK-6484): the user was able to trigger a new query whilst another was in progress.
In order to fix this we've come up with a custom solution that adds a div layer on top of the chips when a request is in progress to swallow all user interactions.
However, this is far from optimal and it would be much better to leave this behavior to the Chip component itself.

Impact

This will remove the need to reinvent the wheel if the same scenario is found again and will centralize the solution to avoid ad-hoc implementations that are hard to track and maintain.

Discussion Questions

• should the look-and-feel of the chip change when in "readonly" mode? Our proposal is that it does not change because it is not a "disabled" state.

Additional considerations

No response

Do you have a visual proposal?

No response

[aweell]

Solved offline