`navigate('relative')` in layout appends to parent route instead of layout's child

[hsab]

Reproduction

--

System Info

System:
    OS: macOS 15.5
    CPU: (8) arm64 Apple M1 Pro
    Memory: 91.27 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.13.0 - ~/.nvm/versions/node/v22.13.0/bin/node
    npm: 10.9.2 - ~/.nvm/versions/node/v22.13.0/bin/npm
    pnpm: 9.15.4 - ~/.nvm/versions/node/v22.13.0/bin/pnpm
  Browsers:
    Chrome: 138.0.7204.158
    Chrome Canary: 140.0.7309.0
    Safari: 18.5
  npmPackages:
    @react-router/dev: ^7.6.2 => 7.6.2
    @react-router/node: ^7.6.2 => 7.6.2
    @react-router/serve: ^7.6.2 => 7.6.2
    react-router: ^7.6.2 => 7.6.2
    vite: 6.3.4 => 6.3.4

Used Package Manager

pnpm

Expected Behavior

I have the following route structure:

const pages = [
  layout('routes/pages/MainLayout.tsx', [
    index('routes/pages/home/ProjectsPage.tsx'),
    layout('routes/pages/flow/FlowLayout.tsx', [
      route('flow/:slug', 'routes/pages/flow/FlowPage.tsx', [
        route('settings', 'routes/pages/settings/SettingsPage.tsx')
      ])
    ])
  ])
];

When relative navigate('settings') is used in FlowLayout or any component that is imported in FlowLayout, the resolved path is always relative to the index.

For example, invoking navigate('settings') via FlowLayout, when the current path is https://acme.com/flow/abc-efg results in https://acme.com/settings.

My expectation is that relative use of navigate should be resolved in relation to window.location.href, resulting in https://acme.com/flow/abc-efg/settings, even when invoked from FlowLayout.

I know the behavior is essentially related to resolvedPath, but is this the expected behavior and mental model?

Actual Behavior

Relative use of navigate('path') should be resolved in relation to window.location.href

[github-actions]

To align with our new Open Governance model, we are now requiring that all issues have a minimal and runnable reproduction. To that end, we're doing some housekeeping in the repo to clean up existing issues that do not have a valid reproduction. This should get us down to a more manageable number of issues and allow us to be more responsive to existing and newly filed issues.

We're using a GitHub actions script to identify issues without a reproduction by looking for a StackBlitz, CodeSandbox, or GitHub link in the issue body. This won't be perfect, so if this issue has a reproduction on another platform, please comment back on here, and we can re-open the issue. Similarly, if there's a reproduction buried in a comment, please move the link into the description and comment back. Please tag @brophdawg11 or @brookslybrand in your comment so we get a notification as well 🙂.

If this issue did not have a reproduction but is still valid, or if you wish to start with a fresh issue, please create a new issue with a fresh reproduction against v7 and link to this issue in the new description.

If this is a feature request, please open a new Proposal Discussion in React Router, and if it gets enough community support, it can be considered for implementation.

If you have any questions, you can always reach out on Discord. Thanks again for providing feedback and helping us make React Router even better!