fix(router): standardize link and resource path resolution

[sy-records]

Summary

Standardize path handling for links, images, and embedded resources.

This change:

• Resolves relative paths from the Markdown page where they are declared by default.
• Resolves absolute paths from the domain root.
• Adds relativeBasePath and absoluteBasePath configuration options.
• Adds a per-element :basepath Markdown attribute.
• Safely falls back to standard path handling when a base path is invalid.
• Prevents configured local base paths from being duplicated.
• Preserves SPA routing for external basePath sources.
• Keeps sidebar links and generated subheadings active when using domain-root hash routes.
• Updates documentation and adds unit, integration, and browser regression tests.

No UI changes are introduced, so before/after screenshots are not applicable.

Related issue, if any:

Fixes #1891

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no api changes)
• Build related changes
• Documentation content changes
• Other (please describe):

For any code change,

• Related documentation has been updated, if needed
• Related tests have been added or updated, if needed

Does this PR introduce a breaking change?

• Yes
• No

Relative links are now resolved from the current Markdown page by default because relativePath defaults to true. Applications that depend on the previous index-relative behavior can restore it with:

window.$docsify = {
  relativePath: false,
};

Absolute paths now resolve from the domain root. Sites that want absolute paths rooted at the Docsify site directory can configure absoluteBasePath.

The default basePath value is now null instead of an empty string.

Tested in the following browsers:

• Chrome
• Firefox
• Safari
• Edge

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docsify-preview	Ready	Preview	Aug 25, 2026 4:54am