Markdown link bug in navbar
See original GitHub issueBug Report
This markdown link:
- [:jp:〉:us:](/ "English")
…has a correct title="English"
when used in a page, but has title="〉"
when used in the navbar document.
Steps to reproduce
Use the markdown link above in a navbar.
What is current behaviour
The generated link has title="〉"
.
What is the expected behaviour
The generated link has title="English"
.
Other relevant information
-
Bug does still occur when all/other plugins are disabled?
-
Your OS: macOS Catalina
-
Browser version: Chrome 86
-
Docsify version: 4.11.6
Link for repro
Mention the docsify version in which this bug was not present (if any)
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
How to add URL link to Navigation Bar on Top - Stack Overflow
I want to add to the navbar a link to an external website, like google. I tried simply adding something like:
Read more >navbar links to /folder instead of linking to folder/index.html #926
At the moment the navbar links to folders which represent the markdown files. This is sufficient if you host your docs on a...
Read more >render_site doesn't create navbar for files which are symlinks
I don't know if this is a bug or WAD but I'm curious about it. I created an rmarkdown website with a navbar...
Read more >Website Navigation - Quarto
Overview. There are a variety of options available for providing website navigation, including: Using top navigation (a navbar) with optional sub-menus.
Read more >Using Markdown for Formatting Content - Bugcrowd Docs
Markdown is a markup language that allows you to format plain text and convert it to HTML. To apply Markdown, add Markdown syntax...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Sorry, I didn’t see that you had created.
I feel like it should have been fixed, You can use this to try.
Fixed via #1360
We will release as soon as possible.