3 ms·

Author here, can you provide the generated policy for me to take a look at?

• miles 6y ago
  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.
  • mandatory 6y ago
    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 https://i.imgur.com/jr534JN.png If you click "Reload policies" under the chrome://policy page does it kick in after ~15 seconds?
    • miles 6y 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 https://tinyapps.neocities.org/cg.mp4 . Tried reloading policies in chrome://policy and waiting 15 seconds as well, but there was no change.
      • lostmsu 6y ago
        Could it be caused by extension load order?
        • miles 6y ago
          I've played with it fairly extensively in a brand new Windows 10 VM, trying various permutations, but still cannot get it to work as intended. superasn's suggestion[0] to set site access permissions via Preferences > Extensions > Details (for the extension in question) > "Site access" worked a treat for me. [0] https://news.ycombinator.com/item?id=23207540 https://news.ycombinator.com/item?id=23207540