Git markdown: frasl works outside tables, not inside #206814
Replies: 6 comments 3 replies
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
|
I can reproduce this issue. It looks like HTML entity parsing is behaving differently in table cells. Could this be fixed so that Thanks! |
|
The issue is caused by the table parser not handling the ⁄ character reference consistently inside table cells. Both ⁄ and ⁄ represent U+2044 (FRACTION SLASH), so they should render identically. The fix is to decode HTML character references in table-cell content using the same entity-decoding logic used for normal Markdown text, rather than treating the named reference differently inside tables. This makes ⁄ render correctly while preserving the existing behavior for numeric references. |
This comment was marked as spam.
This comment was marked as spam.
|
Thanks for confirming. I agree that the difference may be related to font/OpenType fraction rendering rather than the Markdown parser itself. I’ll add the browser and OS details to the report so the rendering behavior can be reproduced more reliably. The 5⁄33 workaround is useful for now, but it would still be good to understand why ⁄ and ⁄ behave differently inside table cells. |


Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
Code Search and Navigation
Body
Consider the infrequently-seen fraction 5⁄33, neatly typeset here using
⁄. So far, so good.Let’s test this in a small table:
⁄⁄Ouch!: not good.
Please can the fraction-slash work inside tables.
Unimportantly, this problem was discovered in the wild.
macOS Tahoe 26.6.2 (25G83); Chrome Version 152.0.7977.66 (Official Build) (arm64). Both believed current as of today, 04 Sept 2026.
All reactions