[matheusmoreira]

Honestly recompilation shouldn't even be necessary, browsers should just let us disable the debugger statement when "clever" sites start taking advantage of it. This usage of debuggers to circumvent our tools is abuse and should be literally impossible unless we consent to it.

Our computers are our realms. God giveth and god taketh away.

[hurutparittya]

Just wait until you won't even be able to open devtools on a WEI protected website. For your security, of course.

[gloosx]

Can't wait when websites start voluntarily cutting themselves out of non-WEI traffic. This means we can take it and serve it, and we will.

[rivo]

Chrome Developer Tools allows this. There's a button in the Source tab to deactivate breakpoints from debug statements. The button looks like an arrow cut in half.

[thunderbong]

This doesn't work for debugger statements.

[KomoD]

You're wrong, it very much does work for debugger

[derefr]

I believe the reason you and the person you're replying to disagree, is that it works for existing debugger statements, but seemingly doesn't work for debugger statements injected after you toggle the flag.

The "disable breakpoints" button is seemingly performing a one-time imperative action on toggle (maybe "find all the breakpoints + debugger statements in existing loaded code, and patch/unpatch them") rather than being a declarative state-change in the system (i.e. "disable this tab's access to the debugger/breakpoint logic itself").

[93po]

I love this exchange. It’s so symbolic of how discussion and disagreement in general works

[chfalck]

If I recall, you can work around this by putting a conditional breakpoint on the debugger statement and then setting its return value to just `false`.