ui5-webcomponents icon indicating copy to clipboard operation
ui5-webcomponents copied to clipboard

[Feature Request]: MultiInput Tokens could be not-removable

Open codefactor opened this issue 3 months ago • 4 comments

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:

  1. Token no longer has a clickable X (dismiss) icon
  2. Token might need to be listed first so as not to block backspace on the other items, also backspace will not delete it
  3. 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.

codefactor avatar Sep 10 '25 13:09 codefactor

Here is a screenshot from an older UI - I do not know off hand what technology it uses ignore the CSS problems:

Image

codefactor avatar Sep 10 '25 13:09 codefactor

Hi @UI5/ui5-team-ctr-ril, could you please take a look?

duygu-rmdn avatar Sep 11 '25 10:09 duygu-rmdn

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

ivoplashkov avatar Sep 14 '25 06:09 ivoplashkov

Design Inner Source item created: SAPDESIGNSYSTEM-403

hristop avatar Oct 03 '25 10:10 hristop