So I went poking around, and the first result that came up for Chrome was Quick Javascript Switcher [0]. Unfortunately, it doesn&#x27;t work like Opera, because it only lets you add site-tweaks that deviate from the global JS on&#x2F;off setting. To change the <i>global</i> setting you need to keep navigating to advanced-settings dialogs.<p>Digging into its JS source-code, the extension calls a browser-API chromeContentSettings.javascript [1]. Now, it sounds like at one point in the past that setting was <i>asynchronous</i>, meaning that disabling JS before visiting a suspect page wasn&#x27;t guaranteed to work anyway [2], but no recent bug-reports or docs mention it, so maybe Chrome fixed that.<p>Still not sure whether there&#x27;s an exploitable race-condition between when the page URL is available versus when the plugin disables JS, I&#x27;m not familiar enough with the relevant events&#x2F;callbacks.<p>[0] <a href="https:&#x2F;&#x2F;chrome.google.com&#x2F;webstore&#x2F;detail&#x2F;quick-javascript-switcher&#x2F;geddoclleiomckbhadiaipdggiiccfje?hl=en" rel="nofollow">https:&#x2F;&#x2F;chrome.google.com&#x2F;webstore&#x2F;detail&#x2F;quick-javascript-s...</a>
[1] <a href="https:&#x2F;&#x2F;developer.chrome.com&#x2F;extensions&#x2F;contentSettings" rel="nofollow">https:&#x2F;&#x2F;developer.chrome.com&#x2F;extensions&#x2F;contentSettings</a>
[2] <a href="https:&#x2F;&#x2F;github.com&#x2F;gorhill&#x2F;httpswitchboard&#x2F;wiki&#x2F;Blocking-javascript-execution-reliably-in-Chromium-based-browsers" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;gorhill&#x2F;httpswitchboard&#x2F;wiki&#x2F;Blocking-jav...</a>