1944472 - fetch keep-alive is not attributed to the parent browsing context

Status: RESOLVED DUPLICATE of bug 1926294

(Core :: DOM: Networking, defect)

Description

[Andrey Lushnikov]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36

Steps to reproduce:

Hi folks! We're coming here from the downstream bug in Playwright: https://github.com/microsoft/playwright/issues/34497

Repro:

1. In Firefox 134, navigate to https://example.com
2. Open DevTools Console
3. evaluate await fetch('/?fetch-keep-alive', { keepalive: true })
4. check DevTools network panel.

ACTUAL: request does not show up in devtools
EXPECTED: request shows up in devtools.

notes

Firefox M133 enabled keep-alive fetch by default. However, the nsHttpChannel instances for these requests do not carry attribution to their relevant browsing context. As a result, Playwright cannot report these requests in its API, because it requires frame information for them.

Probably for the same reason, these requests do not show up in the DevTools Network panel.

I'm not sure if this is anyhow helpful, but there's a speculative fix to add associated browsing context to these requests which looks like this: https://github.com/aslushnikov/juggler/commit/30b05ab1132a6023c4a281bf568496f05c4381c8

Note that this fix (ab)uses the workerAssociatedBrowsingContextId to store the association for the keep-alive fetch requests with their parent frames.

Comment 1

[BugBot [:suhaib / :marco]]

The Bugbug bot thinks this bug should belong to the 'Core::DOM: Networking' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 2

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Maybe a dupe of bug 1926294?