Support Initially Expanded Accordions (`<details open>`)
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 50/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- html, javascript, markdown
- 领域
- frontend
调研方向
The payload names no files, so search the codebase for where details and summary are handled in the Markdown rendering path, and check whether the HTML sanitizer strips the open attribute. The open or closed state must also survive reopening the note, which may involve the note-saving path. Done when <details open> renders expanded, plain <details> stays collapsed, and users can still toggle both.
由索引模型根据 Issue 内容生成。
描述
Nextcloud Notes already supports collapsible sections (accordions) using the HTML <details> and <summary> elements.
However, these sections are always displayed in a collapsed state by default.
In HTML, the open attribute allows a <details> element to be expanded immediately when the page is loaded.
For example:
<details open>
<summary>Title</summary>
Content that is visible by default.
</details>
Currently, there appears to be no way to achieve this behavior in Nextcloud Notes.
Suggested Improvement
Please support the open attribute for <details> elements, allowing accordion sections to be expanded by default.
The expected behavior would be:
<details>— collapsed by default.<details open>— expanded by default.- Users can still manually expand or collapse either type.
- The initial expanded or collapsed state is preserved when reopening the note.
Expected Benefit
This would provide greater flexibility when organizing longer notes with collapsible sections.
Some sections are intended to remain visible by default, while others should only be expanded when needed. Supporting both behaviors would make accordions considerably more useful and bring Nextcloud Notes closer to standard HTML functionality.
- 主要语言
- JavaScript
- 星标
- 739
- 派生
- 162
- 平均合并
- 19 小时 23 分钟
- 30 天内合并 PR
- 49
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
nextcloud/notes 的其他 Issue
-
bug need to reproduce
难度 2/5 1-3 小时 新手友好度 84/100
维护者通常 1 天内回复
-
bug need to reproduce
难度 2/5 1-3 小时 新手友好度 88/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 86/100
维护者通常 1 天内回复
-
bug need to reproduce
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
feature request needs discussion
难度 1/5 1 小时以内 新手友好度 62/100
nextcloud/notes#1344 · 1 条评论 ·
维护者通常 1 天内回复
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 77/100
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 80/100
MagicMirrorOrg/MagicMirror#4310 · 1 条评论 · 1 个 reaction ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
bluerobotics/Cockpit-docs#48 ·
-
难度 2/5 1-3 小时 新手友好度 78/100
tc39/proposal-temporal#3332 ·
-
难度 2/5 1-3 小时 新手友好度 78/100
opennextjs/opennextjs-cloudflare#1461 ·
维护者通常 1 天内回复