Live data from Hacker News

Chrome Inspector Detector

adamschwartz.co

31–40 of 92 posts

Re: Chrome Inspector Detector

#31
post #24

Defeated: javascript:clearTimeout(setTimeout(function(){}, 1) - 1);

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.

Re: Chrome Inspector Detector

#33

Earlier quoted context omitted.

Does that make profiling unusable?

It does, but you usually don't want to profile other dev's pages; here is another solution that doesn't make profiling unusable: chrome.inspector.detector = function(){ return {open:false}} But a more aggresive solution is this one: console = undefined; var iframe = document.body.appendChild(document.createElement("iframe")); iframe.style.display = "none"; window._console = iframe.contentWindow.console And you can us…

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.

Re: Chrome Inspector Detector

#34
post #11

Oh, the evil things I could do with this to coworkers who try to debug my Javascript code. Oh, the evil things I could do...

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.

Re: Chrome Inspector Detector

#37
post #11

Oh, the evil things I could do with this to coworkers who try to debug my Javascript code. Oh, the evil things I could do...

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.

Or perhaps you want to make it so that when someone tries to inspect a DOM element, the element turns into a youtube video of Rick Astley singing "Never Gonna Give You Up." --Just sayin...

Re: Chrome Inspector Detector

#38
post #25

How do I press ⌘ on Linux?

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.

Re: Chrome Inspector Detector

#39
A developer could use this to kill all the DOM nodes on the page when the console was opened. This might be the next generation of:

    img.onclick="javascript:function(){alert('Don\'t steal!');return false}"

Re: Chrome Inspector Detector

#40

Earlier quoted context omitted.

It does, but you usually don't want to profile other dev's pages; here is another solution that doesn't make profiling unusable: chrome.inspector.detector = function(){ return {open:false}} But a more aggresive solution is this one: console = undefined; var iframe = document.body.appendChild(document.createElement("iframe")); iframe.style.display = "none"; window._console = iframe.contentWindow.console And you can us…

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 doesn't matter what your intentions are; eventually it will be used to annoy some developers, lets just hope that it doesn't become something common.
Post reply on HN