You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I performed a cursory search of the issue tracker to avoid opening a duplicate issue
Your issue may already be reported.
I tried to reproduce the issue when...
uBlock Origin is the only extension
uBlock Origin with default lists/settings
using a new, unmodified browser profile
I am running the latest version of uBlock Origin
I checked the documentation to understand that the issue I report is not a normal behavior
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
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"}
Install uBlock Origin
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
uBlock Origin version: 1.20.0
Browser Name and version: Chrome 75.0.3770.100
Operating System and version: Window 10
The text was updated successfully, but these errors were encountered:
I never really completed usage of assetsBootstrapLocation through admin settings. I have fixed this locally, but I do not want to hold back the current release candidate -- the change needs to be tested through a beta build, so I will have to publish it once current release candidate reaches stable release.
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 inassets.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
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"}
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
The text was updated successfully, but these errors were encountered: