UI exploration: consistent UI pattern for user confirmation
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 25/100
- Issue 类型
- 功能
- 描述清晰度
- 需要澄清
- 活跃度
- 停滞
- 技术栈
- html
- 领域
- design, documentation, frontend
调研方向
Review app/templates/custom-elements/security-dialog.html and the linked Static IP change, then inventory confirmation behavior for the other listed dialogs and destructive actions. Define the desired confirmation pattern in the style guide and apply the agreed rules throughout the UI; completion should cover the listed operations consistently.
由索引模型根据 Issue 内容生成。
描述
I don’t think we follow a deliberate pattern in the UI as to when we require confirmation after button clicks in dialogs. E.g.:
- In the upcoming “Static IP” feature, we’ll have a separate confirmation prompt before removing the static IP address.
- In the
<security-dialog>component, we have a confirmation prompt when toggling off the auth requirement. - Apart from that, I don’t think we have such a confirmation in any of our other dialogs, including the ones that carry out destructive and potentially “harmful” operations, such as:
- Removing individual users
- Disabling the HTTPS enforcement
- Changing the hostname (which causes a device reboot)
- Removing disk images (which are potentially very slow to upload)
Not having any confirmation for these kinds of operations actually makes me feel slightly uneasy. (I’m not sure how e.g. customers feel about that, though, or whether we have ever received “angry” feedback about this.)
In any event, I think we should define our desired UX pattern for user confirmation in the style guide, and then roll out the rules in the entire UI.
UI-wise, there are different patterns for user confirmation. Apart from the aforementioned separate confirmation step/prompt, there are also more light-weight patterns we could consider.
- 主要语言
- Python
- 星标
- 3.5k
- 派生
- 292
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
tiny-pilot/tinypilot 的其他 Issue
-
bug medium
难度 2/5 1-3 小时 新手友好度 62/100
tiny-pilot/tinypilot#1419 ·
-
bug
难度 5/5 一周以上 新手友好度 15/100
tiny-pilot/tinypilot#1961 ·
-
enhancement
难度 5/5 一周以上 新手友好度 35/100
tiny-pilot/tinypilot#1929 · 3 条评论 ·
-
bug
难度 3/5 1-2 天 新手友好度 35/100
tiny-pilot/tinypilot#1899 · 1 条评论 ·
-
难度 4/5 3-5 天 新手友好度 35/100
tiny-pilot/tinypilot#1896 ·
查看 tiny-pilot/tinypilot 的全部 Issue
相似的 Issue
-
bug needs-triage priority:medium
难度 2/5 1-3 小时 新手友好度 86/100
yeongseon/azure-functions-logging-python#583 ·
维护者通常 1 天内回复
-
documentation needs-triage priority:medium
难度 2/5 1-3 小时 新手友好度 85/100
yeongseon/azure-functions-validation-python#546 ·
维护者通常 1 天内回复
-
PHP workflow streaming requests buffer the full SSE response可能已有人在做 @Winoren 今天认领。 未关闭review: medium
难度 2/5 1-3 小时 新手友好度 84/100
langgenius/dify#44270 · 1 条评论 · 1 个 reaction ·
维护者通常 1 天内回复
-
P4: low
难度 2/5 1-3 小时 新手友好度 82/100
jeffknupp/association#523 ·
-
bug help wanted
难度 2/5 1-3 小时 新手友好度 65/100
DarkStarSystems/pcons#229 ·
维护者通常 1 天内回复