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
Both VS Code and GitHub use a GitHub-flavored Markdown engine and auto-create jumpable/anchor links in both VS Code and GitHub (using the HTML id attribute) when using headings. If there are non-supported characters they are replaced with a hyphen - (and lower-cased but not relevant here), e.g.:
🤖 Features -> #-features
which works fine, in both GitHub and VS Code (example repository) but fails on the Marketplace, which as mentioned in the official documentation [see markdown field] uses the same GitHub-flavored Markdown but the links stop working (example extension) because it does NOT replace the non-supported characters with a hyphen -, it strips them completely, rendering jumpable links broken on the Marketplace.
Upon inspection of the extension's page, we can clearly see that the id does not comply with the GitHub-flavored anchor links rendering.
Describe the bug
From
microsoft/vscode#224644 (comment)
Both VS Code and GitHub use a GitHub-flavored Markdown engine and auto-create jumpable/anchor links in both VS Code and GitHub (using the HTML
id
attribute) when using headings. If there are non-supported characters they are replaced with a hyphen-
(and lower-cased but not relevant here), e.g.:🤖 Features
->#-features
which works fine, in both GitHub and VS Code (example repository) but fails on the Marketplace, which as mentioned in the official documentation [see
markdown
field] uses the same GitHub-flavored Markdown but the links stop working (example extension) because it does NOT replace the non-supported characters with a hyphen-
, it strips them completely, rendering jumpable links broken on the Marketplace.Upon inspection of the extension's page, we can clearly see that the
id
does not comply with the GitHub-flavored anchor links rendering.Marketplace HTML source code
Steps to Reproduce:
The text was updated successfully, but these errors were encountered: