Closed
Bug 1637838
Opened 5 years ago
Closed 2 years ago
Propagate loaderId to non-Document request and response events
Categories
(Remote Protocol :: CDP, defect, P2)
Remote Protocol
CDP
Tracking
(Not tracked)
RESOLVED
INACTIVE
People
(Reporter: impossibus, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [puppeteer-beta2-mvp])
This is a follow-up from the patch series on Bug 1599260, where Network.requestWillBeSent and Network.responseReceived get a loaderId if they correspond to a Document request.
However, request/response events for sub-resources (scripts, images, etc) should also have this same loaderId. Same for redirects.
|
Reporter | |
Comment 1•5 years ago
|
||
It might help to change how the loaderId is propagated to the Page domain as well, as suggested in: https://phabricator.services.mozilla.com/D74580?id=275658#inline-435618
|
||
Updated•4 years ago
|
Whiteboard: [puppeteer-beta-reserve] → [puppeteer-beta2-mvp]
|
Assignee | |
Updated•4 years ago
|
Component: CDP: Network → CDP
|
|
||
Comment 2•2 years ago
|
||
We are currently not working on CDP.
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INACTIVE
You need to log in
before you can comment on or make changes to this bug.
Description
•