-
Notifications
You must be signed in to change notification settings - Fork 30
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
Support embedding local paths using file:// #46
Comments
Would accept a PR that does this |
Was there not a PR already submitted for this?
…On Tue, Jul 9, 2019, 3:44 PM Jarrett Widman, ***@***.***> wrote:
Would accept a PR that does this
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#46?email_source=notifications&email_token=ABQPQIVK6VG4STSDJCNB3QLP6TTAXA5CNFSM4H4N35N2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZRKE3I#issuecomment-509780589>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABQPQISVVDS2XOXEEI24T2TP6TTAXANCNFSM4H4N35NQ>
.
|
Hello, I have an issue related to this one working with absolute local paths. Currently, the file URL scheme is not supported ( <link rel="stylesheet" href="file:///absolute/path/to/style.css"> To get rid of this issue, I pre-process the HTML file and remove It works on Windows (I get a path like I don't see how to solve this problem except by implementing the file URL scheme (to be able to provide FS absolute path) but I don't know enough about it to propose a good implementation right now. What is your opinion on this subject? PS : apart from this issue, @jrit, thanks for this very good tool, you really made my job easier when I built my last project! |
If
file://
is encountered, web-resource-inliner should correctly embed the file referenced. Currently it just appends the entire link to therelativeTo
path, which causes inline-ing to fail. For example, ifrelativeTo
is set to/a/b/c
, the linkfile:///x/y/z.js
gets translated to/a/b/c/file:/x/y/z.js
.The text was updated successfully, but these errors were encountered: