Implement "network.responseStarted" event
Categories
(Remote Protocol :: WebDriver BiDi, task, P1)
Tracking
(firefox110 fixed)
| Tracking | Status | |
|---|---|---|
| firefox110 | --- | fixed |
People
(Reporter: whimboo, Assigned: jdescottes)
References
(Blocks 4 open bugs, )
Details
(Whiteboard: [webdriver:m5][wptsync upstream][webdriver:relnote])
Attachments
(3 files)
| Assignee | ||
Updated•3 years ago
|
| Assignee | ||
Comment 1•3 years ago
|
||
Let's discuss if we want to keep this in m5, it might be at risk
| Assignee | ||
Comment 2•3 years ago
|
||
Removing triage keyword, we are already discussing about when to end the milestone or not.
| Assignee | ||
Updated•3 years ago
|
| Assignee | ||
Comment 3•3 years ago
•
|
||
Hi Valentin,
Question about nsIChannel's protocolVersion. In our current CDP implementation this is what we use to retrieve the protocol used for a given response. I am checking if I could reuse this for our WebDriver BiDi implementation. The specification for the protocol we should expose in our network events is at https://pr-preview.s3.amazonaws.com/w3c/webdriver-bidi/pull/204.html#get-the-protocol , the most important part being:
If response’s final connection timing info is not null, set protocol to response’s final connection timing info's ALPN negotiated protocol.
Does this match nsIChannel protocolVersion? If yes, do you know when we can start reading this on the channel? If not, do you have any suggestion to get the correct value here?
Thanks!
Edit: I should have read the idl first :) it looks like this is pretty self explanatory:
/**
* Returns the network protocol used to fetch the resource as identified
* by the ALPN Protocol ID.
*
* @throws NS_ERROR_NOT_AVAILABLE if called before the response
* has been received (before onStartRequest).
*/
[must_use] readonly attribute ACString protocolVersion;
but let me know if you have any concern around this nonetheless.
| Assignee | ||
Updated•3 years ago
|
| Assignee | ||
Updated•3 years ago
|
| Assignee | ||
Updated•3 years ago
|
| Assignee | ||
Comment 4•3 years ago
|
||
| Assignee | ||
Comment 5•3 years ago
|
||
Depends on D165431
| Assignee | ||
Comment 6•3 years ago
|
||
Depends on D165432
Comment 7•3 years ago
|
||
(In reply to Julian Descottes [:jdescottes] from comment #3)
Does this match nsIChannel
protocolVersion? If yes, do you know when we can start reading this on the channel? If not, do you have any suggestion to get the correct value here?
Yes, the timing protocolVersion is the same from nsIChannel.protocolVersion - we set it here
Note that for cached resources, we might report the protocol version used to get the original resource - which I believe is not spec compatible.
Comment 10•3 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/4cd27b33734e
https://hg.mozilla.org/mozilla-central/rev/ba47533a1f81
https://hg.mozilla.org/mozilla-central/rev/abe601ec2aa5
| Reporter | ||
Updated•3 years ago
|
Description
•