Skip to content
This repository has been archived by the owner on May 12, 2020. It is now read-only.

What's next for .dotjs addon? #51

Open
eridal opened this issue Mar 1, 2017 · 1 comment
Open

What's next for .dotjs addon? #51

eridal opened this issue Mar 1, 2017 · 1 comment

Comments

@eridal
Copy link
Contributor

eridal commented Mar 1, 2017

With the upcoming changes to Firefox, what's the idea for the extension?

At some point, will it just stop working?

@DonKult
Copy link

DonKult commented Sep 13, 2017

As the repo has an "[unmaintained]" in the description by now I guess that question is implicitly answered… so, just in case someone is looking for alternatives or trying to pick up the pieces:

Webextensions have no direct way of accessing the local filesystem ATM (and I don't see that changing soon or – at all), so to have functionality similar to dotjs an extension has basically two options:
a) Pull files from the web/import manually via "open file" dialog/edit in browser. Tampermonkey does that, the webext port of Greasemonkey, too. AMO sports a few more implementations with varying features: Feel free to pick your poison.
b) Make use of a host application, which from an addon-dev-PoV allows you to do everything you might like, including filesystem access, but as a user you need to install another application alongside the extension… inconvenient at the very least. (beware, shameless plug right ahead) I personally went that route in my dotPageMod as I value file access for myself over ease of use – before you get your hopes up through, that isn't feature-compatible with dotjs either.

Have fun modifying the internet & take care. :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants