-
-
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
fix: sidebar active class and expand don't work as expect when use "space" in markdown filename #1454
Conversation
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/docsify-core/docsify-preview/lmdo37xnk |
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 92c6810:
|
Thanks for this! I think this looks good. |
|
|
||
await page.click('a[href="#/test"]'); | ||
await expect(page).toEqualText('.sidebar-nav li[class=active]', 'Test'); | ||
expect(page.url()).toMatch(/\/test$/); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! I get a good warm feeling of Docsify stability improving now!
Summary
This PR fixes URL decoding problem in sidebar, reported in #1032. It builds on previous work in #1043, but with rebased and updated fix (just 1 line now).
What kind of change does this PR introduce? (check at least one)
If changing the UI of default theme, please provide the before/after screenshot:
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
fix #xxx[,#xxx]
, where "xxx" is the issue number)fix sidebar active class and expand don't work as expect when use "space" in markdown filename #1032, close fix #1032 #1043
You have tested in the following browsers: (Providing a detailed version will be better.)
If adding a new feature, the PR's description includes:
To avoid wasting your time, it's best to open a feature request issue first and wait for approval before working on it.