4 ms·
Naturally this sort of issue has been reported in the past: https://bugs.chromium.org/p/chromium/issues/detail?id=672625 https://bugs.chromium.org/p/chromium/is
by missblit 5y ago
Naturally this sort of issue has been reported in the past: https://bugs.chromium.org/p/chromium/issues/detail?id=672625 https://bugs.chromium.org/p/chromium/issues/detail?id=672625
From the comments on that bug there's other ways to detect devtools (including timing attacks), and it wouldn't be worthwhile to track down every possible case.
As someone who uses devtools debugging a lot I think that answer is reasonable, these kinds of shenanigans mostly only slow down and amuse expert debuggers.
- josephcsible 5y ago> it wouldn't be worthwhile to track down every possible case. I disagree with this conclusion. I think websites being able to detect or interfere with devtools should be considered a security bug. Do we give up on stopping XSS and memory corruption because it's too hard to detect every possible case of them too?