This feature has been removed from the Web standards. Though some browsers may still support it, it is in the process of being dropped. Avoid using it and update existing code if possible; see the compatibility table at the bottom of this page to guide your decision. Be aware that this feature may cease to work at any time.

The deprecated context read-only property of the Request interface contains the context of the Request (e.g., audio, image, iframe). This defines what sort of resource is being fetched. This has been replaced by the destination property.

The context of a request is only relevant in the ServiceWorker API; a service worker can make decisions based on whether the URL is for an image, or an embeddable object such as a <video>, iframe, etc.

Note: You can find a full list of the different available contexts including associated context frame types, CSP directives, and platform feature examples in the Fetch spec request context section.


var myContext = request.context;


A RequestContext value.


In the following snippet, we create a new request using the Request.Request() constructor (for an image file in the same directory as the script), then save the request context in a variable:

var myRequest = new Request('flowers.jpg');
var myContext = myRequest.context; // returns the empty string by default


Specification Status Comment
The definition of 'context' in that specification.
Living Standard Initial definition

Browser compatibility

FeatureChromeEdgeFirefoxInternet ExplorerOperaSafari
Basic support42 — 46 ?39 — 421 No28 — 29 No
FeatureAndroid webviewChrome for AndroidEdge mobileFirefox for AndroidOpera AndroidiOS SafariSamsung Internet
Basic support42 — 4642 — 46 ? No No No4.0

1. see bug 1188062 for more information.

See also

Document Tags and Contributors

Last updated by: Sheppy,