3 ms·
Disabling javascript breakpoints usually does the trick. Devtools detection is often done by having a `debugger;` statement somewhere and timing of it triggered
by Boltgolt 4y ago
Disabling javascript breakpoints usually does the trick. Devtools detection is often done by having a `debugger;` statement somewhere and timing of it triggered
- runlevel1 4y agoA lot of them dynamically generate new anonymous functions to get around this. Last I looked (~1 year ago I think) neither Chrome nor Firefox supported disabling the keyword completely. Do you know if that's changed?
- tenplusfive 4y agoOn Firefox its in the Debugger Tab of the DevTools. On the top right you can deactivate all breakpoints (which includes the debugger statement). There is a similar button on chrome, but I am not sure if that also applies to the debugger statement.