Open fthommen opened 1 year ago
Maybe next year. It requires a full rewrite to convert the extension from a legacy extension to a WebExtension.
ok. Next year is near :-). But thanks anyway for considering at all
Working on it (because I want to get away from that permission), but it takes time.
Closing in favor of https://github.com/jobisoft/quicktext/issues/371
Both issues have been closed but it seems like this issue has not been resolved. Could you please update the status of it?
Fair point. Expect a new version this summer. Here is the todo list.
The WebExtension development branch is still using some Experiment code, but I think we can get rid of all of it.
The add-on reads templates from the user's profile folder. That has to change, and I will store templates in local storage. "Global" templates can be provisioned using the managed storage. Alternatively, templates can be provisioned via HTTP(S) imports on startup (the URL can be provisioned via managed storage).
This is used to read and include images in templates. My proposal is to let users import images into Quicktext (store the image source in local storage / local IndexDB) and let templates reference images by an identifier.
WebExtension can open FilePickers, but only from a web page using <input type="file" />
. However, Quicktext also has two menu entries to include local text/html files. I need to make the menu open a small popup, where the user is prompted to click on the "open file" button.
I still include the LegacyPrefs API to allow admins to provision overrides for defaultImport
and templateFolder
, both will be dropped in favor of managed storage.
Would it be possible to reduce the required permissions of the quicktext plugin? I'd really like to use it, but permission requests like
from a third-party plugin software will always and immediately be denied by me (and I assume also by many others :-) )