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

Allow defining a custom assets.json without adminSettings #3539

Open
9 tasks done
celenityy opened this issue Jan 28, 2025 · 0 comments
Open
9 tasks done

Allow defining a custom assets.json without adminSettings #3539

celenityy opened this issue Jan 28, 2025 · 0 comments

Comments

@celenityy
Copy link

Prerequisites

  • I verified that this is not a filter list issue. Report any issues with filter lists or broken website functionality in the uAssets issue tracker.
  • This is NOT a YouTube, Facebook or Twitch report. These sites MUST be reported by clicking their respective links.
  • This is not a support issue or a question. For support, questions, or help, visit /r/uBlockOrigin.
  • I performed a cursory search of the issue tracker to avoid opening a duplicate issue.
  • The issue is not present after disabling uBO in the browser.
  • I checked the documentation to understand that the issue I am reporting is not normal behavior.

I tried to reproduce the issue when...

  • uBO is the only extension.
  • uBO uses default lists and settings.
  • using a new, unmodified browser profile.

Description

AFAICT, when deploying uBlock Origin, the only way to define a custom assets.json file is via adminSettings.

Ex. for Firefox's 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.

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 of adminSettings, 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 of adminSettings.

uBO version

1.62.0

Browser name and version

Firefox 134.0.2

Operating System and version

N/A

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

No branches or pull requests

1 participant