about:config parameter access for use with SDK, where/how to request?
Hello,
I'm a regular user and I use 4 dozen addons to have mostly security features and a few other additional features.
Since no add-on can offer a toggle to change dom.event.clipboardevents.enabled within the GUI, I asked myself why. Some addon developer just mentioned briefly that it's not that easy to interact with the parameters of about:config.
Surely there are already dozens of concerns about this that lead to the decision of what is possible and what is not right now, but in this particular case it's useful - and some workarounds may be harder / heavier in code or may not be possible at all.
As soon as parameters of about:config can be easily changed, other add-ons could also use this feature and thus their code could be streamlined.
For example access to WebRTC, UserID or the Javascript setting or for accessibility.blockautorefresh, accessibility.typeaheadfind, app.shield.optoutstudies.enabled, browser.fullscreen.autohide, browser.newtab.preload, network.dns.disablePrefetch, pdfjs.disabled, network.http.referer.trimmingPolicy and many others that I didn't mention would be useful as addons to manage these on a site / tab basis!
So I would like to ask where to request something like this and how to properly fit it into the terminology that the moz:devs need to understand?
Many Thanks
All Replies (2)
Add-on questions should be posted in the add-ons forum; https://discourse.mozilla-community.org/c/add-ons
That is a limitation for Web extensions. Legacy extensions (56 and older) were able to access and modify prefs, but Web extensions can only use the available APIs to modify settings and not make changes to prefs directly.