28803 2015-06-12 17:55:23 +0000 RequestContext value "serviceworker" is not observable 2015-06-14 16:08:50 +0000 1 1 1 Unclassified WHATWG Fetch unspecified PC All RESOLVED FIXED P2 normal Unsorted 1 ehsan annevk mike sideshowbarker+fetchspec oldest_to_newest 120954 0 ehsan 2015-06-12 17:55:23 +0000 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? 120958 1 annevk 2015-06-13 06:07:11 +0000 That is a good point. This might also go for various reports features, such as cspreport. 120975 2 ehsan 2015-06-13 21:45:20 +0000 (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. 120979 3 annevk 2015-06-14 16:08:50 +0000 https://github.com/whatwg/fetch/commit/1cc2584d1174b65bd076be3a75b9250016b5c191 See https://github.com/w3c/network-error-logging/issues/54 for further reports discussion.