1938529 - myhmshome.com - Fetch event in Firefox Service Workers does not include clientId

Status: RESOLVED DUPLICATE of bug 1487534

(Core :: DOM: Service Workers, defect, P3)

Description

[Raul Bucata]

Environment:
Operating system: Windows 10
Firefox version: Firefox 133.0

Steps to reproduce:

1. Register a service worker with a fetch event listener:

   self.addEventListener('fetch', (event) => {
   console.log('Client ID:', event.clientId);
   });

2. Open a page controlled by the service worker.

3. Trigger a fetch request (e.g., reload the page).

4. Observe

Expected Behavior:
The clientId property should be populated with the ID of the client initiating the request

Actual Behavior:
clientId is null for all fetch events.

Notes:

• Reproduces regardless of the status of ETP
• Reproduces in firefox-nightly, and firefox-release
• Does not reproduce in chrome

Created from https://github.com/webcompat/web-bugs/issues/145387

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The severity field is not set for this bug.
:denschub, could you have a look please?

For more information, please visit BugBot documentation.

Comment 2

[Eden Chuang[:edenchuang]]

I think this is probably a duplicate of bug 1487534.

According to the code comments, currently we only setup FetchEvent.clientId for subresource requests.

Will double-check if subresource requests also gets an empty ClientID.