undefined | Better HN

0 pointsmiles6y ago0 comments

Thanks very much for replying.

Here is the generated reg file:

  Windows Registry Editor Version 5.00
  
  [HKEY_LOCAL_MACHINE\Software\Policies\Google\Chrome]
  "ExtensionSettings"="{\"*\":{\"runtime_blocked_hosts\":[\"*://ycombinator.com\",\"*://boh.com\"]}}"

Tested in a new Windows 10 x64 (2004) VM with a new install of Google Chrome 81.

0 comments

3 comments · 1 top-level

mandatory6y ago· 2 in thread

How strange, it works for me (although it took a second to propagate) - testing with a Win10 x64 VM as well: https://i.imgur.com/jr534JN.png

If you click "Reload policies" under the chrome://policy page does it kick in after ~15 seconds?

milesOP6y ago

Thank you - it must be me. Had the same issue in a macOS 10.12 VM with Chrome 81. Here's a screen recording of the issue in the Windows 10 x64 (2004) VM: https://tinyapps.neocities.org/cg.mp4 . Tried reloading policies in chrome://policy and waiting 15 seconds as well, but there was no change.

lostmsu6y ago

Could it be caused by extension load order?

1 more reply

j / k navigate · click thread line to collapse