This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 28803 - RequestContext value "serviceworker" is not observable
Summary: RequestContext value "serviceworker" is not observable
Status: RESOLVED FIXED
Alias: None
Product: WHATWG
Classification: Unclassified
Component: Fetch (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: Unsorted
Assignee: Anne
QA Contact: sideshowbarker+fetchspec
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-06-12 17:55 UTC by Ehsan Akhgari [:ehsan]
Modified: 2015-06-14 16:08 UTC (History)
1 user (show)

See Also:

Attachments

Description Ehsan Akhgari [:ehsan] 2015-06-12 17:55:23 UTC 
Since service worker scripts can never be intercepted, there is no way to create a Request object with a context attribute equal to "serviceworker".  Perhaps we should remove this enum value?
Comment 1 Anne 2015-06-13 06:07:11 UTC 
That is a good point. This might also go for various reports features, such as cspreport.
Comment 2 Ehsan Akhgari [:ehsan] 2015-06-13 21:45:20 UTC 
(In reply to Anne from comment #1)
> That is a good point. This might also go for various reports features, such
> as cspreport.

Yeah, but those should be possible to intercept.  But it's hard to tell since those specs are typically not written in terms of fetch.  At any rate, I fixed the interception of CSP reports in Gecko, so they should be successfully reflected to the fetch event as a Request with "cspreport" context.