feat: jumps to anchor in tabbed page

[blakef]

We use tabs to nest whole pages. This means deep links might not aleady have the anchor referenced id on the page. For example:

https://reactnative.dev/docs/environment-setup#ruby

Only applies if the 'React Native CLI Quickstart' -> macOS -> iOS tabs have been selected. There's no guarantee this is the case until the document has loaded and the application have updated the DOM. Once a bunch of PRs have landed (), this type of link will work as expected:

https://reactnative.devdocs/environment-setup?os=macos&platform=ios&guide=native&package-manager=npm#rubys-bundler

This jump-to behaviour should only run on the initial load.

Dependencies

This can go in before, it'll just be a noop until it lands.

• feat: tabs now support deep-linking #3619

Demo

CleanShot.2023-03-16.at.13.40.46.mp4

[netlify]

✅ Deploy Preview for react-native ready!

Name	Link
🔨 Latest commit	5aaefc0
🔍 Latest deploy log	https://app.netlify.com/sites/react-native/deploys/64131deb101a3a000889866b
😎 Deploy Preview	https://deploy-preview-3626--react-native.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[motiz88]

There's no guarantee this is the case until the document has loaded and the application have updated the DOM.

We should probably migrate to a Next.js server-rendered site at some point...

[Simek]

We should probably migrate to a Next.js server-rendered site at some point...

We are not using Next, we use Docusuaurus to power the site, which only supports SSG and SSR only partially.

[motiz88]

@Simek Just to clarify: I'm aware that the site currently uses Docusaurus. I'm saying we might want to consider moving to a different stack.

[Simek]

@motiz88 It would be a quite a big and complex task, probably even bigger than migration to V2 (which took few months and leverage the dedicated MHL group help), so not sure if it is worth the effort if only SSR is a gain, and we will need to reimplement a lot of features like versioning, MDX handling, remark plugins etc., but we definitely can discuss that.