First time anchor URL navigation locks sidebar highlighting after yarn build

[KyleJShaver]

• I confirm that this is an issue rather than a question.

Bug report

When opening a new tab in the browser and navigating directly to an anchor within a page, selecting other anchors will scroll there, but not update the sidenav to show the newly selected option, but only in the yarn build version of the code. This will work properly using yarn dev.

Version

vuepress@1.0.0-alpha.44, latest master

Steps to reproduce

Navigating to Front Matter in the Markdown page of the v1 documentation will work correctly. Navigating to another anchor, either by clicking or scrolling, will update the hash in the URL, but will not update the selected item in the sidebar.

What is expected?

The nav items in the sidebar should be activated when navigating through elements.

What is actually happening?

The original anchor navigated to is the only item that will display as active in the sidebar.

Other relevant information

• Your OS: macOS Mojave 10.14.3
• Node.js version: v11.12.0
• Browser version: Chrome 73.0.3683.86, Firefox 66.0.1, Safari 12.0.3
• Is this a global or local install? Local
• Which package manager did you use for the install? Yarn

[meteorlxy]

It's an known issue of TOC.

If you enter the markdown page directly, the total site will break, not only the header anchor. And you will find the TOC is rendered twice, which is the cause of the bug.

[ulivz]

@shigma Could you follow up on this ASAP? If it's not easy to solve, please roll back to the original TOC.

[shigma]

Fixed at #1524.

Actually it is a bug of markdown-it-toc, which will generate <div> in <p> (incorrect html). In fact, 0.x docs have the same problem.

However, in 1.x docs, table of contents is rendered by a Vue component. When Vue hydrates the corrented html, SSR mismatch is encountered, which leads to this issue.

[ulivz]

Actually it is a bug of markdown-it-toc, which will generate <div> in <p> (incorrect html). In fact, 0.x docs have the same problem.

Aren't you fixing it now?

[lijiahao8898]

which version can fix this bug? i have the same problem. :(