-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
links not working properly for quoted headings #1965
Comments
Hi @yogitheboss , IIRC, It has been fixed, plz update the docsify version |
@Koooooo-7 , I checked again but still the problem persists . I am using latest version of docsify but still the links aren't working. |
I see, I understand the issue now. Normally, I believe it should not be treat as the same.
and
I suppose that you may need surround with The heading is
and when you have the anchor in the content you can do like this.
|
I think I have got my answer , Thanks for responding @Koooooo-7 I am closing the issue |
@Koooooo-7 the custom id is working with docsify but markdown renderer isn't rendering it properly |
Bug Report
Steps to reproduce
create a navigation list using
if we create a heading
"link1_heading"
"link2_heading"
the links doesn't work in docsify generated webpage as the id attribute is "quotlink1_headingquot"
What is current behaviour
the links doesn't work if quotation is included in the name , as id generated of the heading is quot_id_quot instead of quot .
What is the expected behavior
the links should work fine as the readme file treats quotes and no quotes the same
Other relevant information
this bug is causing the https://p5js.org/contributor-docs/#/./contributor_guidelines page's some links to not work
eg. "found a bug" , "Existing Feature Enhancement" etc.
New Feature Request
Discussion"
Bug does still occur when all/other plugins are disabled?
Your OS: windows 10
Node.js version: v16.13.2.
npm/yarn version: v8.3.2
Browser version: v109.0.5414.75
Docsify version: 4.4.4
Docsify plugins:
Please create a reproducible sandbox
Mention the docsify version in which this bug was not present (if any)
The text was updated successfully, but these errors were encountered: