New issue
Advanced search Search tips

Issue 828777 link

Starred by 1 user
Status: Duplicate
Merged: issue 731604
Owner: ----
Closed: Apr 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Fetches from a worker should have a different client ID to the page

Project Member Reported by jakearchibald@chromium.org, Apr 4 2018 
https://worker-client-id-demo.glitch.me/

The fetch from the worker should have a different client ID to the page.

Mozilla have created a WPT for this https://bugzilla.mozilla.org/show_bug.cgi?id=1451124.

Comment 1 by falken@chromium.org, Apr 4 2018

Mergedinto: 731604
Status: Duplicate (was: Untriaged)
Yea this is basically issue 731604 and maybe others. We don't support dedicated worker as a first-class client yet, and instead fetches from it are treated as fetches from the parent document.

Comment 2 by bke...@mozilla.com, Apr 4 2018 

Please be aware that I received a question from a site running into interop problems because of this.  And it seems edge/safari have matched issue 731604's incorrect behavior unfortunately.

Comment 3 by falken@chromium.org, Apr 4 2018 

Understood.
►

Sign in to add a comment