Skip to content
This repository has been archived by the owner on Oct 24, 2020. It is now read-only.

dev tools not detectable in chrome anymore ? #109

Open
Procyon-b opened this issue Dec 2, 2018 · 6 comments
Open

dev tools not detectable in chrome anymore ? #109

Procyon-b opened this issue Dec 2, 2018 · 6 comments

Comments

@Procyon-b
Copy link

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

@jspenguin2017
Copy link

Still detectable: https://output.jsbin.com/cecuzeb/

@Procyon-b
Copy link
Author

You're correct. Your test indicate so.
Sorry for the false alarm. :)

@jspenguin2017
Copy link

A patch was merged just now that allow pausing JavaScript on a page before opening DevTools.
https://chromium-review.googlesource.com/c/chromium/src/+/1372658

@mapx-
Copy link

mapx- commented Dec 14, 2018

"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:

  • open chrome://inspect
  • select 'Pages'
  • click the 'pause' link next to the page you would like to freeze."

@superpoincare
Copy link

Maybe just fixed in Chromium and yet to arrive in Chrome?

@jspenguin2017
Copy link

jspenguin2017 commented Jan 6, 2019

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.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants