Couldn't the devtools listener shenanigans be solved merely by putting a "pause" button in the browser chrome (possibly through an extension)? Browsers are alre

Couldn't the devtools listener shenanigans be solved merely by putting a "pause" button in the browser chrome (possibly through an extension)? Browsers are already throttling CPU usage when the tab isn't visible, so it doesn't seem like it would be too difficult to just throttle to 0 with a toggle. Even better-- have the pause button in devtools window, "pause" by default when you open devtools, and then unpause once something gets mutated/re-layout'd. I guess you'd still need to protect the devtools shortcut key so that any DOM shenanigans are guaranteed to get invoked after the devtools listener. But browsers already have all kinds of crazy edge-cases in the name of security (e.g., no manual triggering of <select> menu). Keeping polymorphic worms from corrupting the devtools state seems rather important by comparison.