51–60 of 92 posts
Earlier quoted context omitted.
But what if he starts using setInterval? A more global solution is to: Open the "sources" panel, click on "Event Listener Breakpoints", then click "set Timer" and just delete the lines where it is calling the detector function.
chrome.inspector.detector=function(){return{}};
This is cool, I used the same technique in the discover-devtools.codeschool.com course for the first challenge.
Earlier quoted context omitted.
It's becoming increasing clear that on HN you're a second class citizen if you don't use Chrome on a Mac and develop on RoR.
That's not contributing anything of value. Offer advice if you've got it, otherwise I don't think theres a valid need to be snarky.
Earlier quoted context omitted.
It may not be clear, but the main use case for this app is not to harm someone, but to aid in development. Perhaps you're making a game and want to pause it or show wireframes when toggling the inspector. Or perhaps you're a designer and you want to show a grid layout whenever you're inspecting elements.
It would be nice to have DOM events (just like onResize), which would only be activated when activating the related option in the console (just like the "Show XHR requests" option). [edit] https://code.google.com/p/chromium/issues/detail?id=223418
Worst case scenario, to defeat this: Save page to local drive, edit JS (and remove this) in your IDE/text editor. Open locally.