This repository has been archived by the owner on Oct 24, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 42
dev tools not detectable in chrome anymore ? #109
Comments
Still detectable: https://output.jsbin.com/cecuzeb/ |
You're correct. Your test indicate so. |
A patch was merged just now that allow pausing JavaScript on a page before opening DevTools. |
"Note that the console.log detection was fixed previously. There is now a way to pause the page before it has a chance to detect devtools. For that you should:
|
Maybe just fixed in Chromium and yet to arrive in Chrome? |
It's available in Chrome 73 (Dev). Also it looks like the new demo got patched. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Has anyone noticed this, or is it new?
I've just noticed this extension, tried several examples and saw boston.com behaving as described.
Then I followed to the theregister's article where a chrome bug is mentioned. In the bug report there is a link to an example. I've tried it and no difference between dev tools displayed or not.
Going back to boston.com, the site still creates its cookies despite the dev tools being opened.
uBO-extra is not installed.
Chrome 70.0.3538.110
The text was updated successfully, but these errors were encountered: