[Feature Request]: MultiInput Tokens could be not-removable
维护者通常 2 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 35/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
- 技术栈
- typescript
- 领域
- frontend
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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
- I’m not disclosing any internal or sensitive information.
- 主要语言
- TypeScript
- 星标
- 1.8k
- 派生
- 290
- 平均合并
- 2 天 13 小时
- 30 天内合并 PR
- 50
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
UI5/webcomponents 的其他 Issue
-
ACC author action
难度 2/5 1-3 小时 新手友好度 78/100
UI5/webcomponents#14273 · 1 条评论 ·
维护者通常 2 天内回复
-
[Button]: crash on Safari 17 due to missing ElementInternals.states guard in _setBadgeOverlayStyle未关闭author action bug TOPIC B
难度 1/5 1 小时以内 新手友好度 87/100
UI5/webcomponents#14270 · 2 条评论 ·
维护者通常 2 天内回复
-
[Feature Request][Side Navigation][A11Y]: Enhance user experience navigating components tree items可能已有人在做 @TeodorTaushanov 于 7 天前认领。 未关闭bug Medium Prio TOPIC RD
难度 2/5 1-3 小时 新手友好度 72/100
UI5/webcomponents#14232 · 1 条评论 · 已指派 1 人 ·
维护者通常 2 天内回复
-
enhancement feature request TOPIC RD
难度 2/5 1-3 小时 新手友好度 68/100
UI5/webcomponents#14222 · 1 条评论 ·
维护者通常 2 天内回复
-
[SF][A11y][ui5-select] Conflicting ARIA: role="combobox" rendered with aria-roledescription="Listbox" (confuses screen-reader users)可能已有人在做 @PetyaMarkovaBogdanova 于 12 天前认领。 未关闭bug Medium Prio TOPIC P
难度 2/5 1-3 小时 新手友好度 67/100
UI5/webcomponents#14212 · 2 条评论 · 已指派 1 人 ·
维护者通常 2 天内回复
查看 UI5/webcomponents 的全部 Issue
相似的 Issue
-
approved check:passed streams:add
难度 1/5 1 小时以内 新手友好度 78/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
duolicious/duolicious#1943 ·
维护者通常 1 天内回复
-
bug needs-triage
难度 2/5 1-3 小时 新手友好度 80/100
nightly-labs/openbot#6451 ·
维护者通常 1 天内回复
-
level1 nsoc26
难度 2/5 1-3 小时 新手友好度 66/100
GauravKarakoti/SecureFlow#1719 ·
维护者通常 1 天内回复
-
complexity: easy good first issue impact: low
难度 2/5 1-3 小时 新手友好度 72/100
ueberdosis/hocuspocus#1211 ·
维护者通常 1 天内回复