Repository navigation
RDoc-4147 Allow linking content from switchable sections - #2707
Open
poissoncorp wants to merge 1 commit into
Open
poissoncorp wants to merge 1 commit into
poissoncorp wants to merge 1 commit into
Conversation
poissoncorp
force-pushed
the
tabs-hash-anchors
branch
from
October 22, 2026 22:58
857ce90 to
b72a52b
Compare
3 of 13 tasks
poissoncorp
force-pushed
the
tabs-hash-anchors
branch
from
October 23, 2026 01:13
b72a52b to
dbe1107
Compare
Lwiel
approved these changes
Oct 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue link
https://issues.ravendb.net/issue/RDoc-4147/Allow-linking-content-from-switchable-sections
Additional description
A link to an anchor or heading inside a non-selected tab now opens that tab and scrolls to the target. Until now the target sat in a
hiddenpanel, so neither the browser nor Docusaurus could scroll to it and the link did nothing. No content changes needed: an<a id="..."/>or a heading inside aTabItemis enough.How it works (
useOpenTabOfHashTargetin the swizzledTabs):Tabs' panels holds it, and selects that tab throughselectValue, the same call a tab click makes.Tabssharing thegroupIdhave switched too.queryStringtab click) is skipped, the same rule as Docusaurus'scrollAfterNavigation.groupId.New
templates/tabspage: basic usage, linking to content inside a tab (with a live example) and the props authors use.Verified on a production build (
build:current) with temporary anchors in a page: page load with#anchorpointing into a hidden tab, in-page links and TOC entries to anchors in other tabs, switching tabs by hand afterwards (also withqueryString), following the same link again, andTabssharing agroupId. Lint, Prettier and typecheck clean.Type of change
/templatesor readme)Changes in docs URLs
/scripts/redirects.jsonfile, setDocuments MovedPR label)Changes in UX/UI
No visual change, so no screenshots: links to anchors inside tabs now open the tab and scroll to the anchor.