mirror of
https://github.com/deepseek-ai/DeepSeek-V3.git
synced 2026-11-05 00:47:48 +00:00
[GH-ISSUE #1280] DeepSeek Web 前端渲染问题反馈 —— 含表格的 Markdown 代码块被错误渲染,无法完整复制原始文本 #830
Labels
No labels
closed-as-stale
enhancement
question
spam
stale
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
deepseek-ai/DeepSeek-V3#830
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @JodieFoster233 on GitHub (May 7, 2026).
Original GitHub issue: https://github.com/deepseek-ai/DeepSeek-V3/issues/1280
问题描述
当模型回复中包含 ```markdown 代码块,且代码块内部含有表格时,界面会将表格错误渲染,导致代码块结构被破坏,无法完整复制原始文本。
复现步骤
"请在单个 Markdown 代码块内输出以下内容,不要做任何额外解释:一个一级标题、一段文字,一个嵌套的 Python 代码块,一个五行五列的表格、一个无序列表,以及一行普通文字。"
实际结果
表格被渲染成可视化表格,代码块标记失效,复制后无法得到原始 Markdown。
预期结果
代码块内所有内容以纯文本原样显示,不被渲染。
相关链接
https://chat.deepseek.com/share/4lwyq8n6blbfvxve2x
环境
@qingkong66 commented on GitHub (May 7, 2026):
@JodieFoster233 Thanks for filing your first issue — and with such a clear reproduction.
Workaround (for now):
When a Markdown code block gets partially rendered (e.g., the table turns into a visual table), copy the already rendered parts and ask the model again to output only the missing pieces (e.g., "please output the table inside the code block as plain Markdown"). Repeat until you recover the full block. It’s manual, but it works.
This is not a fix — it’s a way to unblock yourself. We’ve logged the rendering defect and will include it in our next feedback batch to the team.
Thanks again for surfacing this.
@github-actions[bot] commented on GitHub (Jun 7, 2026):
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you believe this issue is still relevant, please leave a comment to keep it open. Thank you for your contributions!
@github-actions[bot] commented on GitHub (Jun 28, 2026):
false