[Bug] Competency Criteria Associations: any/all differs from the design, inline score error breaks the layout on narrow screens
维护者通常 1 天内回复
@illiphilli 已经在做这个了。
开始于 2026年11月16日。
评估
这个 Issue 还没有评估数据。
描述
Description
On the Manage & Apply Competencies page, the editable controls added in https://github.com/openedx/openedx-core/issues/794 (frontend-app-authoring https://github.com/openedx/frontend-app-authoring/pull/3358) differ from the design in Figma, and the score field's validation message breaks the rule box layout on narrower screens.
Environment: Master Sandbox (https://apps.master.openedx.io/authoring/), user with edit access to the course (for example a global staff user).
Steps to reproduce
- Open
/authoring/taxonomy/<id>/competenciesfor a Competency taxonomy (e.g. https://apps.master.openedx.io/authoring/taxonomy/182/competencies) and select a leaf competency that has saved associations, so that the "Competency Criteria Associations" block shows a group card with at least two rule boxes. - Look at the "By completing any of the following" line.
- In one rule box, enter the score of another rule box in the same group and press Enter.
- Reduce the window width.
Issues
1. The any/all operator uses a different font color and weight
- Expected: "any"/"all" is shown in the gray color from the design and weight 700.
- Actual: "any"/"all" is shown in blue (link-style button) and weight 400.
2. The validation message breaks the layout on narrow screens
- Expected: the validation message is shown without breaking the rule box layout at any supported width.
- Actual: the message is placed on the same line, to the right of "% or higher". When the window is narrowed, the rule box layout breaks: at 863px and below for "Another rule box in this group already uses this score.", and at 743px and below for "Enter a whole number from 0 to 100.". The breaking width depends on the message length.
- 主要语言
- Python
- 星标
- 10
- 派生
- 35
- 平均合并
- 5 天 2 小时
- 30 天内合并 PR
- 23
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
openedx/openedx-core 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 79/100
openedx/openedx-core#934 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
openedx/openedx-core#922 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 75/100
openedx/openedx-core#831 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 85/100
openedx/openedx-core#827 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 35/100
openedx/openedx-core#935 ·
维护者通常 1 天内回复
查看 openedx/openedx-core 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
can4hou6joeng4/boss-agent-cli#1487 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 64/100
-
难度 2/5 1-3 小时 新手友好度 76/100
btclib-org/btclib-wallet#1045 ·
维护者通常 1 天内回复
-
area-templates triage:bot-seen triage:needs-human
难度 2/5 1-3 小时 新手友好度 75/100
microsoft/aspire#22356 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100