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

Aperta
  • Qualcosa non va?
#12,290 4 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Ferma
Stack tecnologico
typescript
Ambito
frontend

Direzione di ricerca

Start by reading the Token and MultiInput component implementations and how tokens are rendered in the More popover. Define the optional non-removable behavior across the dismiss icon, backspace handling, ordering, and popover presentation. Done means one token can remain protected while other tokens remain removable, including in the proposed Recipients use case.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Design Pending feature request Medium Prio SAP SF TOPIC RL
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
  • I’m not disclosing any internal or sensitive information.
Lingua principale
TypeScript
Stelle
1.8k
Fork
290
Merge medio
2g 13h
PR unite (30g)
50

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di UI5/webcomponents

Tutte le issue di UI5/webcomponents

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.