A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://github.com/uBlockOrigin/uBlock-issues/issues/666 below:

uBlock does not appear to honor overriding default assets.json via Chrome policy · Issue #666 · uBlockOrigin/uBlock-issues · GitHub

Prerequisites Description

Attempting to designate our own default assets.json via Chrome policy (per https://github.com/gorhill/uBlock/wiki/Deploying-uBlock-Origin#modifying-the-list-of-stock-assets) doesn't seem to function as expected.
In my debugging, I see that the URL we designated for the location of our default assets.json is parsed by storage.js but I don't actually see our assets.json attempt to get pulled from the webserver as I believe it's designed to in assets.js. Instead, it uses the bundled assets.json.

A specific URL where the issue occurs

[A specific URL is MANDATORY for issue happening on a web page, even if it happens "everywhere"]

Steps to Reproduce
  1. Set Chrome extension policy via registry
    Key: HKLM\Software\Policies\Google\Chrome\3rdparty\extensions\cjpalhdlnbpafiamejdnhcphjbkeiagm\policy
    adminSettings with value {"timeStamp":1562713627423,"version":"1.20.0","assetsBootstrapLocation":"https://my-url-here.com/assets.json"}
  2. Install uBlock Origin
  3. View settings and see only default assets.json is loaded
Expected behavior:

We expect the our designated custom assets.json to be loaded from the URL we specify.

Actual behavior:

The extension's bundled assets/assets.json is loaded.

Your environment

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4