Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Markdown path IntelliSense suggests header becomes an encoded string #142330

Closed
satokaz opened this issue Feb 6, 2022 · 0 comments · Fixed by #142392
Closed

Markdown path IntelliSense suggests header becomes an encoded string #142330

satokaz opened this issue Feb 6, 2022 · 0 comments · Fixed by #142392
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug markdown Markdown support issues verified Verification succeeded
Milestone

Comments

@satokaz
Copy link
Contributor

satokaz commented Feb 6, 2022

Does this issue occur when all extensions are disabled?: Yes

  • VS Code Version: 1.64.0
  • OS Version: macOS 12.1

This is a bug in the Markdown path IntelliSense feature added in vscode 1.64.
The encoded string is suggested as a link in the markdown header.

Steps to Reproduce:

  1. Create a header with characters such as Japanese (etc...)
  2. Show suggestions with Markdown path IntelliSense

image

@mjbvz mjbvz added this to the February 2022 milestone Feb 7, 2022
@mjbvz mjbvz added bug Issue identified by VS Code Team member as probable bug markdown Markdown support issues and removed unreleased Patch has not yet been released in VS Code Insiders labels Feb 7, 2022
@jrieken jrieken added the verified Verification succeeded label Feb 23, 2022
@github-actions github-actions bot locked and limited conversation to collaborators Mar 24, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug markdown Markdown support issues verified Verification succeeded
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants
@jrieken @mjbvz @satokaz and others