You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you create a header markdown header, an anchor is created for you and special characters are removed and spaces are trimmed. This works great... mostly. There are 2 issues:
When an emoji is used, there are sometimes invisible characters left behind.
When there's a space before or after the emoji, the space isn't getting trimmed.
Proposal
Remove special and invisible characters first, then trim spaces.
Example
## 🙋♀️ Ask a question
To the naked eye, this looks like #-ask-a-question, which is mostly fine barring the extra space. But when you see this in the browser, it's rendered as #%EF%B8%8F-ask-a-question.
This should render as #ask-a-question without the invisible characters or extra space.
The text was updated successfully, but these errors were encountered:
I think replacing such characters with hyphens might be more predictable / less surprising. So #-ask-a-question is the result I feel would be most intuitive. (That said, I agree that removing them altogether is an improvement over the current situation.)
Proposal
When you create a header markdown header, an anchor is created for you and special characters are removed and spaces are trimmed. This works great... mostly. There are 2 issues:
Proposal
Remove special and invisible characters first, then trim spaces.
Example
## 🙋♀️ Ask a question
To the naked eye, this looks like
#-ask-a-question
, which is mostly fine barring the extra space. But when you see this in the browser, it's rendered as#%EF%B8%8F-ask-a-question
.This should render as
#ask-a-question
without the invisible characters or extra space.The text was updated successfully, but these errors were encountered: