-
-
Notifications
You must be signed in to change notification settings - Fork 8.6k
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
feat(v2): highlight items in the table of content #1896
Conversation
Deploy preview for docusaurus-preview ready! Built with commit 542b7c9 |
Deploy preview for docusaurus-2 ready! Built with commit 542b7c9 |
* Convert sitemap plugin to TypeScript Test - enabled the sitemap plugin in the v2 website and verified that the sitemap is created after running `docusaurus build`. * Addressing review comments
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.
If i go to https://deploy-preview-1896--docusaurus-2.netlify.com/docs/introduction/#gitbook
The Gitbook is not highlighted, i have to scroll around or resize first.
Compare it to https://docusaurus.io/docs/en/installation#running-the-example-website
Update: Clicking the right sidebar directly also doesnt highlight that particular section
Strange it works fine for me in Chrome (I'm on Linux), but not in Firefox 🤷♂️ |
…cebook#1898) * perf(v2): reduce bundle size significantly with super short chunk name and registry * changelog * use hash:8 as id for better long term caching * even shorter filename. slice contenthash
* fix(v2): align search icon on small width device * nits * nits
There are many misbehaviors from preview:
The behaviors said above appears in both Firefox and Chrome, the screen record I have here shows Chrome: I think the implementation in #1524 is correct and the comments around it serves as good pseudocode. Suggest that we follow it directly. |
Both things work fine for me (the gitbook highlight works fine, also clicking the sidebar update directly) I am going to play around until I can reproduce it.
OK, I am going to test in firefox and see what's going on.
If you want me too I can see the issues that are happening (some of them also happen in v1). Please tell me if you want me to fix the issues described in the comments or you prefer to delete this PR. I did put time on this but I completely understand if you prefer to go another way. |
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.
I think the issues need to be fixed before merging, the behavior doesn't feel correct to me atm. |
I wont merge until both of u approve :) Just putting stamp 😃 |
Great! I am going to work on the fixes. Thanks |
* change(v2): refactor dark toggle into a theme * follow how themes resolve files * let theme hook to pick up default theme by itself
…acebook#1871) * fix issue#1752 when element in side nav is hovered over the color changes. * Update main.css
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 work. This is one of the features that I'm highly anticipating too, thank you for working on this.
Tested on Chrome, Safari and Firefox, and contrary to what @lex111 experienced, the result on Firefox is the best 😮
Some suggestions I have:
- Create a custom hook so that this is reusable by non-theme classic Docs components. In future if we want to have a Bootstrap theme, we can reuse this hook.
- The hook should take in the corresponding class names as function arguments.
DocItem
should import this hook and invoke it with the classnames specific to this theme.
- You might want to take a look at the implementation of feat: highlight nav item in onPageNav ToC #1524 for inspiration on how this was achieved in v1. v1's behavior is great and battle-tested (no complaints about it so far). cc @tusharf5 if he's interested in helping to review.
* misc(v2): address comments * misc(v2): update CHANGELOG
* feat(v2): allow line highlighting * Refactor: use parse-numeric-range for parsing * Add line highlighting for live code blocks * feat(v2): add sticky footer (facebook#1855) * feat(v2): add sticky footer * Update CHANGELOG-2.x.md * Update CHANGELOG-2.x.md * fix(v2): remove empty doc sidebar container (facebook#1870) * docs: showcase user Amphora (facebook#1873) * Add Amphora Data link to users Adds Amphora Data to the list of users * Add Amphora Data logo * fix case of image path * Move Image into users directory * use black amphora image * fix(v2): fix search input blur on desktop (facebook#1874) * docs(v2): showcase user mbt-bundle (facebook#1875) * feat(v2): postcss should only use stage 3 features instead of stage 2 (facebook#1872) * feat(v2): add ability expand all items in doc sidebar (facebook#1876) * feat(v2): add ability expand all items in doc sidebar * Fix tests * Refactor: use themeConfig * Improve docs * Revert unnecessary changes * Refactor: better consistency * Revert extra change * Refactor: use useDocusaurusContext to get config value * chore(v2): update changelog * chore(v2): update showcase and broken link * perf(v2): disable hash for css modules localident in dev (facebook#1882) * perf(v2): disable hash for css modules localident in dev * changelog * feat(v2): display footer in docs page for consistency (facebook#1883) * feat(v2): display footer in docs page * nits * address review * nits * docs(v2): fix format inline code (facebook#1888) * docs(v2): add docs on useful client api (facebook#1890) * docs(v2): add docs on useful client api * Update docusaurus-core.md * Update website/docs/docusaurus-core.md * Update website/docs/docusaurus-core.md * Update website/docs/docusaurus-core.md * Update website/docs/docusaurus-core.md * docs(v2): update config docs (facebook#1885) * fix(v2): do not show categories with empty items (facebook#1891) * styles(v2): update infima and fix styles (facebook#1892) * fix(v2): wrong css class * v2.0.0-alpha.31 * chore(v2): update docs and changelog * docs(v2): update plugins, presets and themes docs (facebook#1889) * docs(v2): update plugins, presets and themes docs * ideal image plugin * proof reading * Merge master * refactor(v2): Convert sitemap plugin to TypeScript (facebook#1894) * Convert sitemap plugin to TypeScript Test - enabled the sitemap plugin in the v2 website and verified that the sitemap is created after running `docusaurus build`. * Addressing review comments * perf(v2): significantly reduce bundle size & initial html payload (facebook#1898) * perf(v2): reduce bundle size significantly with super short chunk name and registry * changelog * use hash:8 as id for better long term caching * even shorter filename. slice contenthash * fix(v2): align search icon on small width device (facebook#1893) * fix(v2): align search icon on small width device * nits * nits * refactor(v2): refactor dark toggle into a hook (facebook#1899) * change(v2): refactor dark toggle into a theme * follow how themes resolve files * let theme hook to pick up default theme by itself * perf(v2): reduce memory usage consumption (facebook#1900) * misc(v1): use primary color for hovered items in table of contents (facebook#1871) * fix issue#1752 when element in side nav is hovered over the color changes. * Update main.css * fix(v1): mobile safari search input misalignment in header (facebook#1895) * misc(v2): v1 backward compatibility for USE_SSH env var (facebook#1880) * misc(v2): address comments * misc(v2): update CHANGELOG
* Update README.md - Fix Broken Link * misc: update URLs to non-HTML versions
…ok#1917) * fix(v2): regression from prioritizing core node_modules logic * nits
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.
@SantiagoGdaR don't do anything until you get approval from Docusaurus devs, this is just my 2 cents.
let tableOfContentLinks = []; | ||
|
||
function getActiveHeaderAnchor() { | ||
const TOP_OFFSET = topOffset; |
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.
Do you really need to create a constant for this when it is used once? I mean, the code is not so big, and there is no point in duplicating the same value in such a way.
In my opinion it is better to do without it:
- if (top >= 0 && top <= TOP_OFFSET) {}
+ if (top> = 0 && top <= topOffset) {}
] = useState(undefined); | ||
|
||
useEffect(() => { | ||
let headersAnchor = []; |
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.
Is not it more correct to call this var that?
headersAnchor
-> headerAnchors
@@ -11,16 +11,26 @@ import Head from '@docusaurus/Head'; | |||
import useDocusaurusContext from '@docusaurus/useDocusaurusContext'; | |||
import useBaseUrl from '@docusaurus/useBaseUrl'; | |||
import DocPaginator from '@theme/DocPaginator'; | |||
import useTableOfContentHighlight from '@theme/hooks/useTableOfContentHighlight'; |
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.
Maybe it makes sense TableOfContent
shorten to simply toc
? It will be easier to read and understand.
useTableOfContentHighlight
->useTocHighlight
tableOfContentLinkClassName
->tocLinkClassName
- And so on
setLastActiveTableOfContentLink(tableOfContentLink); | ||
} | ||
|
||
function getAnchorValue(tableOfContentLink) { |
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.
I would consider this solution, it will be faster.
function getAnchorValue(tocLink) {
return decodeURIComponent(
tocLink.href.substring(tocLink.href.indexOf('#') + 1)
);
}
function getActiveHeaderAnchor() { | ||
const TOP_OFFSET = topOffset; | ||
let index = 0; | ||
let activeHeaderAnchor; |
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.
You must probably explicitly set the default value.
let activeHeaderAnchor = null;
packages/docusaurus-theme-classic/src/theme/hooks/useTableOfContentHighlight.js
Outdated
Show resolved
Hide resolved
if (activeHeaderAnchor) { | ||
let index = 0; | ||
let itemHighlighted = false; | ||
tableOfContentLinks = document.querySelectorAll( |
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.
Hmm, I would prefer to use the old-school document.getElementsByClassName
(sort of like it's even faster), since the selection goes only by class and it is assumed that only the class will be used, otherwise you need to rename the parameter to tableOfContentLinkSelector
and continue use querySelectorAll
🤔
const [ | ||
lastActiveTableOfContentLink, | ||
setLastActiveTableOfContentLink, | ||
] = useState(undefined); |
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.
Use null
instead of undefined
Thanks @lex111, personally I agree on most of the changes you propose. I am going to work on them or respond with a comment in the case I think we should discuss something further. |
* docs(v2): theme, plugin, and preset config * change tabs to spaces * change theme example
This is much stable and more performant
* fix(v2): allow to create tabs with only one item It was not possible to have tabs containing only one tab item, so the code below crashed ``` <Tabs defaultValue="SomeFile.js" values={[ { label: "SomeFile.js", value: "SomeFile.js" } ]} > <TabItem value="SomeFile.js"> Tab content </TabItem> </Tabs> ``` * Update index.js
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.
Looks good overall. Let's implement some of the suggestions by @lex111 and we're good to merge.
Thanks for working on this!
I understand correctly that we will implement all my suggestions, except the last one, about the concatenating of classes? |
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.
I've made the changes. Merging it 🎉
Motivation
Implement the highlight functionality for the table of content links on the scroll and on click events.
The implementation is partially based on the solution implemented in v1 but it is drastically changed to make better use of React.
Resolve issue: #1752
Also relates to: #1524
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
When clicking on any of the links of a table of content or while you scroll on a section that contains a table of content you are going to notice that the table of content has the link of the section you have on the screen highlighted.
Tested on Safari and Chrome.
Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/facebook/docusaurus, and link to your PR here.)