[Feature Request]: MultiInput Tokens could be not-removable
Feature Request Description
The <Token> web component passed to <MultiInput> can sometimes not be removed at all. For example, a use case came up for a "Recipients" field where the first recipient is not removable, but any of the other recipients are removable. This is different from a read only multi input where all tokens are not removable.
Proposed Solution
Have a boolean property on Token like "not-removable" or some other similarly named property that is optional and when supplied will trigger the changes:
- Token no longer has a clickable X (dismiss) icon
- Token might need to be listed first so as not to block backspace on the other items, also backspace will not delete it
- Token when showing in the More popover should not have an X button or it should be disabled.
Proposed Alternatives
We can get close to this by implementing the React code such that the closeIcon is an empty icon, with an onClick that stops propogation, however, this has a couple of issues for example the more popup still shows it as removable since the closeIcon doesn't get used there.
We can also filter out the non-removable items entirely and show them in a separate place somehow or make it implied (e.g. a note that says the recipients always includes the author or something else). But this requires a change to the design.
Organization
SuccessFactors
Additional Context
No response
Priority
Medium
Privacy Policy
- [x] I’m not disclosing any internal or sensitive information.
Here is a screenshot from an older UI - I do not know off hand what technology it uses ignore the CSS problems:
Hi @UI5/ui5-team-ctr-ril, could you please take a look?
Hello colleagues,
I think this is similiar to having both readonly and not readonly tokens in one Tokenizer, however instead of readonly it should be "not-removable". This should be discussed with design, whether they see this fit or not.
Best regards, Ivaylo
Design Inner Source item created: SAPDESIGNSYSTEM-403