Skip to content
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 for file:///path/to/file needed #2

Open
reikred opened this issue Nov 22, 2019 · 3 comments
Open

support for file:///path/to/file needed #2

reikred opened this issue Nov 22, 2019 · 3 comments
Assignees

Comments

@reikred
Copy link

@reikred reikred commented Nov 22, 2019

I could not get the addon to open URLs of the type file:///path/to/file, which is what I need it for :).
NEW INFORMATION INCLUDED :-).

I'm adding this issue here after adding it yesterday in the old/dead code location BulkURLOpener-Firefox and getting a response there. The old repository was just archived yesterday so I guess this is the right place to revive the issue, hopefully, with some additional info that may help find a viable solution.

It should be easy to fix for Chrome Browser but with Firefox it may only work if an <input> element is used to create the input list of URLs, as explained in

QUOTE: https://wiki.mozilla.org/WebExtensions/Filesystem#Firefox
Firefox
WebAPI
Currently there is the File and Directory Entries API, which is a non-standard API based off of Chrome’s implementation. Outside creation and modification of a virtual filesystem for a given app, it permits read access to a file when using an <input> element or drag and drop.

Do you think there may exist a solution based in using <input>?

@github-actions

This comment has been minimized.

Copy link

@github-actions github-actions bot commented Nov 22, 2019

Hello! Thank you for letting me know about your issue. I will hopefully reply to you soon to help resolve your issue. :)

@EuanRiggans

This comment has been minimized.

Copy link
Owner

@EuanRiggans EuanRiggans commented Nov 23, 2019

Thanks for letting me know about the issues yestarday in the old repo, that one is now archived as the two previously separate code-bases have no been merged into one.

I will look into the Chrome implementation of this feature tomorrow, as you say it should be possible as Chrome is less restrictive with APIs when compared to Firefox.

And thanks for providing the Firefox web api workaround, which I will also look into, and if it provides a stable solution to the issue I will implement it for the project.

@EuanRiggans EuanRiggans self-assigned this Nov 23, 2019
@EuanRiggans EuanRiggans added the bug label Nov 23, 2019
@EuanRiggans

This comment has been minimized.

Copy link
Owner

@EuanRiggans EuanRiggans commented Nov 24, 2019

I did some research into the issue you've mentioned, and I have not been able to find a solution that would be viable for this extension.

Both Chrome and Firefox appear to block opening of file:// resources from a script (for good reason). And any potential workarounds I found would not work in this extension or would not be stable. For example the workaround that you provided, it would be a little complex to implement especially when a user would be opening several file:// urls at one time.

Thanks again for letting me know about this issue, I will leave this issue open so that if there are any solutions which would make this feature possible I will implement them.

EuanRiggans added a commit that referenced this issue Feb 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.