The requirement is not without side-effects.<p>From the chrome developer group[1]<p>> The devmode switch also enables other features e.g. chrome.declarativeNetRequest.onRuleMatchedDebug which may severely reduce the performance of the content blocking extensions, depending on how it's used.<p>Unless they are happy with degraded performance or needing to switch to developer mode often, users may have to chose between ad-blocking and custom scripts.<p>Chrome's current stance is that users have no right/legitimate business case running custom scripts on a site. You are allowed to do it only in the context of development. On the flip-side, this also means some features in development mode can potentially be restricted in the future saying they are non-essential for development.<p>Given all these hostile decisions, it is still our choice on whether we want to switch to a better browser or become the proverbial frog in the pot.<p>[1] <a href="https://groups.google.com/a/chromium.org/g/chromium-extensions/c/bdnjlMNzQqA/m/Kotb3-eVAAAJ" rel="nofollow noreferrer">https://groups.google.com/a/chromium.org/g/chromium-extensio...</a>