Closed
Bug 1605720
Opened 6 years ago
Closed 1 year ago
Not calling Target.setDiscoverTargets() will cause hangs in waiting for "Target.activateTarget"
Categories
(Remote Protocol :: CDP, defect, P3)
Remote Protocol
CDP
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: whimboo, Unassigned)
References
Details
I have seen that a couple of times for browser chrome tests. Specifically when opening a new tab and waiting for the target to be activated. If Target.setDiscoverTargets() isn't called before, the test hangs until the timeout.
We should investigate why this is happening.
For the moment I will file a separate bug that will move the call to Target.setDiscoverTargets() into head.js, which ensures that it is always called.
|
Assignee | |
Updated•4 years ago
|
Component: CDP: Target → CDP
|
||
Updated•3 years ago
|
Severity: normal → S3
|
Reporter | |
Comment 1•1 year ago
|
||
CDP is deprecated and we no longer actively work on this protocol. As such lets close out this bug.
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•