Chrome Inspector Detector
81–90 of 92 posts
Re: Chrome Inspector Detector
#82Earlier 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.
DHH would certainly agree: http://david.heinemeierhansson.com/arc/000433.html
Re: Chrome Inspector Detector
#83Re: Chrome Inspector Detector
#84 Profile 'Profile 13' started. chrome.inspector-detector.js:16
Profile 'Profile 13' finished. chrome.inspector-detector.js:17
Console was clearedRe: Chrome Inspector Detector
#85Oh, 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
#86How do I press ⌘ on Linux?
Now you know how to press it.
Your next problem is that much Linux software (Chrome included) insists on using the MS Windows convention of overloading Control for menu shortcuts. This is a great nuisance when you want to be able to use, for example, both Control-V (the conventional LNEXT character in *nix consoles) and GUI-V (the conventional Paste shortcut in GUIs).
Pre-Linux X programs tended to get this right, since they were not focussed on slavishly imitating MS Windows. Apple got it right somewhat accidentally — the original Mac keyboard had no Control key at all, and it got added to support familiar editing and remote terminal uses.
Re: Chrome Inspector Detector
#87A 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
#88you simply used chrome api :)
Re: Chrome Inspector Detector
#89Worst case scenario, to defeat this: Save page to local drive, edit JS (and remove this) in your IDE/text editor. Open locally.