uBOL adding dashboard suppression

[dluong06]

As others have started doing, we wanted to get ahead of MV3 implantation in our environment. However first install launch of the dashboard may cause some users to freak out.

Similar to this discussion, can I request that dashboard suppression be added?
#35

[gorhill]

gorhill/uBlock@b9f3523

[dluong06]

Noticed this is committed to 1.0.23.8155 in the public release in Chrome Web Store. In testing it does not seem to work for the public release but it does work in the dev build 1.51.1b23.

Added picture for registry entry ref.

[gorhill]

it does work in the dev build 1.51.1b23.

1.51.1b23 is uBlock Origin, it does not support that setting. I implemented the setting for uBlock Origin Lite (uBO Lite).

The Chrome store version of uBO Lite supports the setting. I tried it locally before publishing and it worked on my side as expected -- using linux. For windows, I wouldn't know how this works. The value for disableFirstRunPage is boolean, this won't work if it's a string.

[gorhill]

This screenshot found at [1] suggests you are missing the policy part under the extension id.

[1] https://github.com/andy-portmen/open-in/issues/36#issuecomment-559789771

---

The documentation for windows also show usage of policy:

.../3rdparty\extensions\gihmafigllmhbppdfjnfecimiohcljba\policy

[dluong06]

Ended up doing a few tests with the information you provided and got it to work. Here is the correct configuration for anyone else that may look this up in the future.

It would be a REG_DWORD with the value of 1 for True within the subkey of "policy" under "ddkjiahejlhfcafbddmgiahcphecmpfh" FOR WINDOWS MACHINES
Full path "Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\3rdparty\extensions\ddkjiahejlhfcafbddmgiahcphecmpfh\Policy"

[gorhill]

Looks like what worked for you is explained here as Option 3:

Booleans are also stored as Dword Values. Use 0 for false and 1 for true.

---

So I suspect if you had used "true" instead of true, it would have worked (Option 2), since JSON.stringify(true) is "true".

[dluong06]

Sorry to bring up this old thread again. MS Edge seems to not process the policy of disableFirstRunPage in the same manner as Chrome despite both being Chromium based. Not sure if this is related to how uBOL finds the policy or an Edge issue.

I've tried this with both the Edge store uBOL and Chrome Store uBOL. I've also tested with diableFirstRunPage = 1 for true in both policy and the extension key itself. Attached screenshots of where MS Edge64 handles forced extension installs and basic testing of the policy.

[gorhill]

how uBOL finds the policy

It's just a standard API, through browser.storage.managed.get(). I don't see documentation specific to Microsoft Edge for that API, they defer to the official Chrome documentation.