Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

This is what happens when websites prevent an open Console/DevTools side panel. They basically have a main loop running, inserting a debugger; statement in various places where they're annoying, and they do that at 30FPS / 32ms so that the DevTools become useless because there's no way to "ignore" debugger statements.


Why would this be a problem? I have a debugger. If you conveniently invoke it for me I can simply delete the offending code.

Also both Chrome and Firefox have a "disable breakpoints" button that would instantly defeat this issue.


This button was added to specifically combat that, and even then it means you can't use breakpoints at all. IMO the missing link is a way to specifically ignore a single debugger call.


TFA has instructions on adding conditional breakpoint with 'false' inside. Wouldn't this work?


Yes, this will work. Sometimes you do it to yourself and you want to ignore the line.


The debugger lets you edit the code in the VM, so if there's a debugger call you don't want you can simply delete it and continue and it'll not show up again until you refresh




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: