Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Update 03-linking-and-navigating.mdx #51084

Merged
merged 2 commits into from
Jun 10, 2023
Merged

Update 03-linking-and-navigating.mdx #51084

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
71ea411
Update 03-linking-and-navigating.mdx
svarunid Jun 10, 2023
710cda3
Merge branch 'canary' into patch-1
svarunid Jun 10, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/02-app/01-building-your-application/01-routing/03-linking-and-navigating.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -95,7 +95,7 @@ export function Navigation({ navLinks }) {

The default behavior of `<Link>` is to [scroll to the top of the route segment that has changed](#focus-and-scroll-management). When there is an `id` defined in `href`, it will scroll to the specific `id`, similarly to a normal `<a>` tag.

To prevent scrolling to the top of the route segment, set `scroll={false}` and pass the add a hashed `id` to `href`:
To prevent scrolling to the top of the route segment, set `scroll={false}` and add a hashed `id` to `href`:

```jsx
<Link href="/#hashid" scroll={false}>
Expand Down