read: a trailing space inside bold, italic or strikethrough is dropped, joining words
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
Start in storage_to_md.go, near renderInline and coalesceSplitMarks, and inspect the table property test referenced in #55. Reproduce the bold, italic, and strikethrough examples through read → publish. Done means trimmed edge spaces are emitted outside the Markdown delimiters so words remain separated, including leading spaces and non-table paragraphs.
由索引模型根据 Issue 内容生成。
描述
Problem
read and export trim the whitespace at the edge of a marked span, and the space is not put back outside the marks, so the words either side of the span's end run together on the next publish. Found by the table property test in #55, on a real page.
Reproduced 2026-09-25 (read → publish):
| storage | read writes | publish sends |
|---|---|---|
<p><strong>bold </strong>next</p> |
**bold**next |
<p><strong>bold</strong>next</p> |
<p><em>x </em>y</p> |
*x*y |
<p><em>x</em>y</p> |
<p><del>lost for </del>13.5h</p> |
~~lost for~~13.5h |
<p><del>lost for</del>13.5h</p> |
The last row is from a real incident table in a personal space: the page shows "…features for13.5h" after a read → update cycle. The Markdown is a fixed point after the first cycle, so no round-trip test notices. It affects every paragraph, not only tables. The Confluence editor produces this shape readily, since a space typed at the end of a bold run stays inside the run.
Notes
- Trimming is right, since CommonMark refuses
**bold **as emphasis (a closing delimiter preceded by whitespace does not close). The fix is to move the trimmed whitespace outside the delimiters:**bold** next. The same goes for a leading space:<strong> bold</strong>should become**bold**. coalesceSplitMarksinstorage_to_md.gohandles a related editor shape (a mark split around a link); the fix probably belongs near where marks are rendered inrenderInline.
- 主要语言
- Go
- 星标
- 2
- 派生
- 0
- 平均合并
- 2 小时 31 分钟
- 30 天内合并 PR
- 59
环境准备
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
mozilla/markfluence 的其他 Issue
-
难度 4/5 3-5 天 新手友好度 48/100
mozilla/markfluence#216 ·
维护者通常 1 天内回复
-
难度 3/5 1-2 天 新手友好度 76/100
mozilla/markfluence#214 ·
维护者通常 1 天内回复
-
难度 3/5 1-2 天 新手友好度 68/100
mozilla/markfluence#213 ·
维护者通常 1 天内回复
-
enhancement
难度 4/5 3-5 天 新手友好度 48/100
mozilla/markfluence#210 ·
维护者通常 1 天内回复
-
documentation
难度 5/5 一周以上 新手友好度 25/100
mozilla/markfluence#209 ·
维护者通常 1 天内回复
查看 mozilla/markfluence 的全部 Issue
相似的 Issue
-
bug needs-triage
难度 2/5 1-3 小时 新手友好度 86/100
DataDog/dd-trace-go#5469 ·
维护者通常 1 天内回复
-
bug tests
难度 2/5 1-3 小时 新手友好度 88/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
l3montree-dev/devguard#3101 ·
维护者通常 1 天内回复
-
area:*of bug
难度 2/5 1-3 小时 新手友好度 78/100
oapi-codegen/oapi-codegen#2593 ·
维护者通常 1 天内回复
-
bug
难度 1/5 1 小时以内 新手友好度 85/100
DaoCloud/DaoCloud-docs#7432 ·
维护者通常 1 天内回复