We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
assets.json
adminSettings
AFAICT, when deploying uBlock Origin, the only way to define a custom assets.json file is via adminSettings.
Ex. for Firefox's policies.json:
policies.json
"3rdparty": { "Extensions": { "uBlock0@raymondhill.net": { "adminSettings": { "assetsBootstrapLocation": "https://example.com/assets.json" } } } }
My understanding is that the use of adminSettings is deprecated and no longer recommended, so it's important to have another way to configure this.
N/A
It should be possible to define a custom assets.json for uBlock Origin without the use of adminSettings, as it's deprecated and not recommended.
AFAIK, it's only possible to define a custom assets.json for uBlock Origin with the use of adminSettings.
1.62.0
Firefox 134.0.2
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Prerequisites
I tried to reproduce the issue when...
Description
AFAICT, when deploying uBlock Origin, the only way to define a custom
assets.json
file is viaadminSettings
.Ex. for Firefox's
policies.json
:My understanding is that the use of
adminSettings
is deprecated and no longer recommended, so it's important to have another way to configure this.A specific URL where the issue occurs.
N/A
Steps to Reproduce
N/A
Expected behavior
It should be possible to define a custom
assets.json
for uBlock Origin without the use ofadminSettings
, as it's deprecated and not recommended.Actual behavior
AFAIK, it's only possible to define a custom
assets.json
for uBlock Origin with the use ofadminSettings
.uBO version
1.62.0
Browser name and version
Firefox 134.0.2
Operating System and version
N/A
The text was updated successfully, but these errors were encountered: