-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
fix: files from basePath should be remoteUrl:false #1660
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.
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
Conversation
This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.
🔍 Inspect: https://vercel.com/docsify-core/docsify-preview/9PEsj4Y74qkJAhpihAttVtDSSv1y
✅ Preview: https://docsify-preview-git-fork-b6pzeusbc54tvhw5jg-bd121d-docsify-core.vercel.app
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 16b5ba5:
|
Uh oh!
There was an error while loading. Please reload this page.
Summary
When using the
basePath
as an absolute url including the domain and the domain ofindex.html
and the domain ofbasePath
are different, Currently, files fetched frombasePath
are treated asisExternal: true
, and I think this behavior is a bug.basePath
is a value that can be entered only with the authority of the document site administrator, and thebasePath
server can also be considered owned by the administrator, so theisRemoteUrl
value should befalse
.What kind of change does this PR introduce?
Bugfix
For any code change,
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
Related issue, if any:
#1659
Tested in the following browsers: