Emit a single network.responseCompleted event for authentication flows
Categories
(Remote Protocol :: WebDriver BiDi, defect, P1)
Tracking
(firefox129 fixed)
Tracking | Status | |
---|---|---|
firefox129 | --- | fixed |
People
(Reporter: jdescottes, Assigned: jdescottes)
References
(Blocks 5 open bugs)
Details
(Whiteboard: [webdriver:m12], [wptsync upstream])
Attachments
(2 files)
At the moment the BiDi + fetch spec expects that only a single network.responseCompleted event should be emitted when we have an authentication sequence, regardless of the number of authentication attempts.
It is unclear if we want to keep this behavior in the long run, Bug 1899604 will be about tracking the related spec discussion and implementing the changes if need be.
This will unblock the "network Page.authenticate should allow disable authentication" puppeteer test.
Assignee | ||
Updated•3 days ago
|
Updated•3 days ago
|
Assignee | ||
Comment 1•3 days ago
|
||
This is compliant with the current specification. All authentication request attempts for the same original request share the same request id, and only a single responseCompleted event should be
emitted.
Assignee | ||
Comment 2•3 days ago
|
||
Depends on D215623
Pushed by jdescottes@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/593b97c86729 [bidi] Only emit a single responseCompleted event for an authentication flow r=webdriver-reviewers,whimboo https://hg.mozilla.org/integration/autoland/rev/cb195cae29c6 [wdspec] Update continueWithAuth tests to check for a single responseCompleted r=webdriver-reviewers,whimboo
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/46998 for changes under testing/web-platform/tests
Comment 5•2 days ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/593b97c86729
https://hg.mozilla.org/mozilla-central/rev/cb195cae29c6
Upstream PR merged by moz-wptsync-bot
Description
•