Rich Diff of Markdown does not work properly

[da-in]

Select Topic Area

Question

Body

Use of GitHub's markdown is very convenient, so it is good to archive documents and is grateful.🥰

However, when our team made a Pull Request, I confirmed that the rich diff did not work well in some cases.

• When the newly created file, i.e. when the generation history is included in the Pull Request, Rich Diff works properly.

• When we modify the markdown file that is already created in the main branch and generate PR, Rich diff does not work and the following statement is printed.

  Oh My
  Sorry... we’re unable to render the document prior to diffing.

• Jupyter Notebook Rich Diff Feedback #37376
  I searched for related issues and confirmed that softwrapping was mentioned in the jupyer notebook rich diff issue.
  Does the plan to improve softwrapping include the above markdown issue?

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[davaya]

This problem has also existed for years on markdown files.

Unreliable Partial Workaround: occasionally switching between line diff and rich diff one or more times will get the rich diff to render, but most attempts fail even after 10 repeats. Yes, intermittent bugs can be difficult to debug, but on many files the error is consistently reproducible.

The stalebot page says: "As you mentioned, many of the questions here are answered by GitHub staff or at least someone from the community."

It would be nice if someone from GitHub staff would chime in and say one of:

• reproduced - working on it
• reproduced - don't care / won't be fixed
• can't reproduce