You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Keeping devtools page closed, so that devtools shouldn't be detected. The page should shown as "Devtools: close".
What did you see instead?
Devtools can be detected as opened while actually not, especially when chromedp.Sleep running.
The page shows that Devtools Opens because of performance impact.
Description
I was very curious about this strange performance issue. By running the code above, the webpage shows the browser with devtools page opening, which was because it detected a performance impact on console.log, console.table or largeArrayCreation within its code. But that should not happen.
I have also check with a python port of cdp client, with the same behaviours as nivagating, sleeping, executing js code and finally click it by calling dispatchMouseEvent, it runs smoothly without any performance impact after multiple attempts.
And it seems that the performance impact may occurred during chromedp.Sleep(). I'm not 100% sure about this. But if I delete all sleeping invocation, there is a chance that the webpage cannot detect any performance issue.
The text was updated successfully, but these errors were encountered:
What versions are you running?
What did you do? Include clear steps.
What did you expect to see?
Keeping devtools page closed, so that devtools shouldn't be detected. The page should shown as "Devtools: close".
What did you see instead?
Devtools can be detected as opened while actually not, especially when
chromedp.Sleep
running.The page shows that Devtools Opens because of performance impact.
Description
I was very curious about this strange performance issue. By running the code above, the webpage shows the browser with devtools page opening, which was because it detected a performance impact on
console.log
,console.table
orlargeArrayCreation
within its code. But that should not happen.I have also check with a python port of cdp client, with the same behaviours as nivagating, sleeping, executing js code and finally click it by calling
dispatchMouseEvent
, it runs smoothly without any performance impact after multiple attempts.And it seems that the performance impact may occurred during
chromedp.Sleep()
. I'm not 100% sure about this. But if I delete all sleeping invocation, there is a chance that the webpage cannot detect any performance issue.The text was updated successfully, but these errors were encountered: