BrowserContext
Added in: v1.8BrowserContexts provide a way to operate multiple independent browser sessions.
If a page opens another page, e.g. with a window.open call, the popup will belong to the parent page's browser context.
Playwright allows creating isolated non-persistent browser contexts with browser.newContext() method. Non-persistent browser contexts don't write any browsing data to disk.
// Create a new incognito browser context
const context = await browser.newContext();
// Create a new page inside context.
const page = await context.newPage();
await page.goto('https://example.com');
// Dispose context once it's no longer needed.
await context.close();Methods
browserContext.addCookies()
Added in: v1.8 asyncAdds cookies into this browser context. All pages within this context will have these cookies installed. Cookies can be obtained via browserContext.cookies().
Usage
await browserContext.addCookies([cookieObject1, cookieObject2]);Arguments
namestringvaluestringurlstring(optional)Either
urlor bothdomainandpathare required. Optional.domainstring(optional)For the cookie to apply to all subdomains as well, prefix domain with a dot, like this: ".example.com". Either
urlor bothdomainandpathare required. Optional.pathstring(optional)Either
urlor bothdomainandpathare required. Optional.expiresfloat(optional)Unix time in seconds. Optional.
httpOnlyboolean(optional)Optional.
secureboolean(optional)Optional.
sameSite"Strict" | "Lax" | "None"(optional)Optional.
partitionKeystring(optional)For partitioned third-party cookies (aka CHIPS), the partition key. Optional.
browserContext.addInitScript()
Added in: v1.8 asyncAdds a script which would be evaluated in one of the following scenarios:
- Whenever a page is created in the browser context or is navigated.
- Whenever a child frame is attached or navigated in any page in the browser context. In this case, the script is evaluated in the context of the newly attached frame.
The script is evaluated after the document was created but before any of its scripts were run. This is useful to amend the JavaScript environment, e.g. to seed Math.random.
Usage
An example of overriding Math.random before the page loads:
// preload.js
Math.random = () => 42;// In your playwright script, assuming the preload.js file is in same directory.
await browserContext.addInitScript({
path: 'preload.js'
});INFO
The order of evaluation of multiple scripts installed via browserContext.addInitScript() and page.addInitScript() is not defined.
Arguments
scriptfunction() | string | ObjectScript to be evaluated in all pages in the browser context.
pathpath(optional)Path to the JavaScript file. If
pathis a relative path, then it is resolved relative to the current working directory. Optional.contentstring(optional)Raw script content. Optional.
Optional argument to pass to
script(only supported when passing a function).exposeFunctionsboolean(optional) Added in: v1.62When set to
true, functions passed insideargare exposed in the page and can be called from the init script. Calling one returns a [Promise] of its result. Under the hood, each function is exposed viapage.exposeFunction(), so it is technically accessible from all frames of the page. Unlike functions passed topage.evaluate(), functions passed to an init script are exposed in every new document, so they survive navigations. Defaults tofalse, in which case functions are not serializable and are silently dropped.
Returns
Promise<Disposable>
browserContext.browser()
Added in: v1.8Gets the browser instance that owns the context. Returns null if the context is created outside of normal browser, e.g. Android or Electron.
Returns
null | Browser
browserContext.clearCookies()
Added in: v1.8 asyncRemoves cookies from context. Accepts optional filter.
Usage
await context.clearCookies();
await context.clearCookies({ name: 'session-id' });
await context.clearCookies({ domain: 'my-origin.com' });
await context.clearCookies({ domain: /.*my-origin\.com/ });
await context.clearCookies({ path: '/api/v1' });
await context.clearCookies({ name: 'session-id', domain: 'my-origin.com' });Arguments
browserContext.clearPermissions()
Added in: v1.8 asyncClears all permission overrides for the browser context.
Usage
const context = await browser.newContext();
await context.grantPermissions(['clipboard-read']);
// do stuff ..
context.clearPermissions();browserContext.close()
Added in: v1.8 asyncCloses the browser context. All the pages that belong to the browser context will be closed.
INFO
The default browser context cannot be closed.
Arguments
browserContext.cookies()
Added in: v1.8 asyncIf no URLs are specified, this method returns all cookies. If URLs are specified, only cookies that affect those URLs are returned.
Arguments
Returns
Promise<Array<Object>>
browserContext.exposeBinding()
Added in: v1.8 asyncThe method adds a function called name on the window object of every frame in every page in the context. When called, the function executes callback and returns a [Promise] which resolves to the return value of callback. If the callback returns a [Promise], it will be awaited.
The first argument of the callback function contains information about the caller: { browserContext: BrowserContext, page: Page, frame: Frame }.
See page.exposeBinding() for page-only version.
Usage
An example of exposing page URL to all frames in all pages in the context:
const { webkit } = require('playwright'); // Or 'chromium' or 'firefox'.
(async () => {
const browser = await webkit.launch({ headless: false });
const context = await browser.newContext();
await context.exposeBinding('pageURL', ({ page }) => page.url());
const page = await context.newPage();
await page.setContent(`
<script>
async function onClick() {
document.querySelector('div').textContent = await window.pageURL();
}
</script>
<button onclick="onClick()">Click me</button>
<div></div>
`);
await page.getByRole('button').click();
})();Arguments
Name of the function on the window object.
Callback function that will be called in the Playwright's context.
Returns
Promise<Disposable>
browserContext.exposeFunction()
Added in: v1.8 asyncThe method adds a function called name on the window object of every frame in every page in the context. When called, the function executes callback and returns a [Promise] which resolves to the return value of callback.
If the callback returns a [Promise], it will be awaited.
See page.exposeFunction() for page-only version.
Usage
An example of adding a sha256 function to all pages in the context:
const { webkit } = require('playwright'); // Or 'chromium' or 'firefox'.
const crypto = require('crypto');
(async () => {
const browser = await webkit.launch({ headless: false });
const context = await browser.newContext();
await context.exposeFunction('sha256', text =>
crypto.createHash('sha256').update(text).digest('hex'),
);
const page = await context.newPage();
await page.setContent(`
<script>
async function onClick() {
document.querySelector('div').textContent = await window.sha256('PLAYWRIGHT');
}
</script>
<button onclick="onClick()">Click me</button>
<div></div>
`);
await page.getByRole('button').click();
})();Arguments
Name of the function on the window object.
Callback function that will be called in the Playwright's context.
Returns
Promise<Disposable>
browserContext.grantPermissions()
Added in: v1.8 asyncGrants specified permissions to the browser context. Only grants corresponding permissions to the given origin if specified.
Arguments
A list of permissions to grant.
DANGER
Supported permissions differ between browsers, and even between different versions of the same browser. Any permission may stop working after an update.
Here are some permissions that may be supported by some browsers:
'accelerometer''ambient-light-sensor''background-sync''camera''clipboard-read''clipboard-write''geolocation''gyroscope''local-fonts''local-network-access''magnetometer''microphone''midi-sysex'(system-exclusive midi)'midi''notifications''payment-handler''storage-access''screen-wake-lock'
The [origin] to grant permissions to, e.g. "https://example.com".
browserContext.isClosed()
Added in: v1.59Indicates that the browser context is in the process of closing or has already been closed.
Returns
boolean
browserContext.newCDPSession()
Added in: v1.11 asyncINFO
CDP sessions are only supported on Chromium-based browsers.
Returns the newly created session.
Arguments
Target to create new session for. For backwards-compatibility, this parameter is named
page, but it can be aPageorFrametype.
Returns
Promise<CDPSession>
browserContext.newPage()
Added in: v1.8 asyncCreates a new page in the browser context.
Returns
Promise<Page>
browserContext.pages()
Added in: v1.8Returns all open pages in the context.
Returns
Array<Page>
browserContext.removeAllListeners()
Added in: v1.47 asyncRemoves all the listeners of the given type (or all registered listeners if no type given). Allows to wait for async listeners to complete or to ignore subsequent errors from these listeners.
Arguments
behavior"wait" | "ignoreErrors" | "default"(optional)Specifies whether to wait for already running listeners and what to do if they throw errors:
'default'- do not wait for current listener calls (if any) to finish, if the listener throws, it may result in unhandled error'wait'- wait for current listener calls (if any) to finish'ignoreErrors'- do not wait for current listener calls (if any) to finish, all errors thrown by the listeners after removal are silently caught
browserContext.route()
Added in: v1.8 asyncRouting provides the capability to modify network requests that are made by any page in the browser context. Once route is enabled, every request matching the url pattern will stall unless it's continued, fulfilled or aborted.
INFO
browserContext.route() will not intercept requests intercepted by Service Worker. See this issue. We recommend disabling Service Workers when using request interception by setting serviceWorkers to 'block'.
Usage
An example of a naive handler that aborts all image requests:
const context = await browser.newContext();
await context.route('**/*.{png,jpg,jpeg}', route => route.abort());
const page = await context.newPage();
await page.goto('https://example.com');
await browser.close();or the same snippet using a regex pattern instead:
const context = await browser.newContext();
await context.route(/(\.png$)|(\.jpg$)/, route => route.abort());
const page = await context.newPage();
await page.goto('https://example.com');
await browser.close();It is possible to examine the request to decide the route action. For example, mocking all requests that contain some post data, and leaving all other requests as is:
await context.route('/api/**', async route => {
if (route.request().postData().includes('my-string'))
await route.fulfill({ body: 'mocked-data' });
else
await route.continue();
});Page routes (set up with page.route()) take precedence over browser context routes when request matches both handlers.
To remove a route with its handler you can use browserContext.unroute().
INFO
Enabling routing disables http cache.
Arguments
urlstring | RegExp | URLPattern | function(URL): booleanA glob pattern, regex pattern, URL pattern, or predicate that receives a [URL] to match during routing. If
baseURLis set in the context options and the provided URL is a string that does not start with*, it is resolved using thenew URL()constructor.handlerfunction(Route, Request): Promise<any> | anyhandler function to route the request.
Returns
Promise<Disposable>
browserContext.routeFromHAR()
Added in: v1.23 asyncIf specified the network requests that are made in the context will be served from the HAR file. Read more about Replaying from HAR.
Playwright will not serve requests intercepted by Service Worker from the HAR file. See this issue. We recommend disabling Service Workers when using request interception by setting serviceWorkers to 'block'.
Arguments
Path to a HAR file with prerecorded network data. If
pathis a relative path, then it is resolved relative to the current working directory.notFound"abort" | "fallback"(optional)- If set to 'abort' any request not found in the HAR file will be aborted.
- If set to 'fallback' falls through to the next route handler in the handler chain.
Defaults to abort.
If specified, updates the given HAR with the actual network information instead of serving from file. The file is written to disk when
browserContext.close()is called.updateContent"embed" | "attach"(optional) Added in: v1.32Optional setting to control resource content management. If
attachis specified, resources are persisted as separate files or entries in the ZIP archive. Ifembedis specified, content is stored inline the HAR file.updateMode"full" | "minimal"(optional) Added in: v1.32When set to
minimal, only record information necessary for routing from HAR. This omits sizes, timing, page, cookies, security and other types of HAR information that are not used when replaying from HAR. Defaults tominimal.urlstring | RegExp(optional)A glob pattern, regular expression or predicate to match the request URL. Only requests with URL matching the pattern will be served from the HAR file. If not specified, all requests are served from the HAR file.
browserContext.routeWebSocket()
Added in: v1.48 asyncThis method allows to modify websocket connections that are made by any page in the browser context.
Note that only WebSockets created after this method was called will be routed. It is recommended to call this method before creating any pages.
Usage
Below is an example of a simple handler that blocks some websocket messages. See WebSocketRoute for more details and examples.
await context.routeWebSocket('/ws', ws => {
const server = ws.connectToServer();
ws.onMessage(message => {
if (message === 'to-be-blocked')
return;
server.send(message);
});
});Arguments
urlstring | RegExp | function(URL): booleanOnly WebSockets with the url matching this pattern will be routed. A string pattern can be relative to the
baseURLcontext option.handlerfunction(WebSocketRoute): Promise<any> | anyHandler function to route the WebSocket.
browserContext.serviceWorkers()
Added in: v1.11INFO
Service workers are only supported on Chromium-based browsers.
All existing service workers in the context.
Returns
Array<Worker>
browserContext.setDefaultNavigationTimeout()
Added in: v1.8This setting will change the default maximum navigation time for the following methods and related shortcuts:
INFO
page.setDefaultNavigationTimeout() and page.setDefaultTimeout() take priority over browserContext.setDefaultNavigationTimeout().
Arguments
browserContext.setDefaultTimeout()
Added in: v1.8This setting will change the default maximum time for all the methods accepting timeout option.
INFO
page.setDefaultNavigationTimeout(), page.setDefaultTimeout() and browserContext.setDefaultNavigationTimeout() take priority over browserContext.setDefaultTimeout().
Arguments
browserContext.setExtraHTTPHeaders()
Added in: v1.8 asyncThe extra HTTP headers will be sent with every request initiated by any page in the context. These headers are merged with page-specific extra HTTP headers set with page.setExtraHTTPHeaders(). If page overrides a particular header, page-specific header value will be used instead of the browser context header value.
INFO
browserContext.setExtraHTTPHeaders() does not guarantee the order of headers in the outgoing requests.
Arguments
headersObject<string, string>An object containing additional HTTP headers to be sent with every request. All header values must be strings.
browserContext.setGeolocation()
Added in: v1.8 asyncSets the context's geolocation. Passing null or undefined emulates position unavailable.
Usage
await browserContext.setGeolocation({ latitude: 59.95, longitude: 30.31667 });INFO
Consider using browserContext.grantPermissions() to grant permissions for the browser context pages to read its geolocation.
Arguments
latitudefloatLatitude between -90 and 90.
longitudefloatLongitude between -180 and 180.
accuracyfloat(optional)Non-negative accuracy value. Defaults to
0.
browserContext.setHTTPCredentials()
Added in: v1.8 asyncSets the credentials for HTTP authentication for this browser context.
INFO
Browsers may cache credentials per origin after a successful authentication, so changing credentials for an origin that has already been authenticated may have no effect.
Arguments
httpCredentialsnull | Object | Array<Object>Pass an array to use different credentials for different origins. The first entry that matches the request origin is used, and entries with no origin match any request.
usernamestringpasswordstringoriginstring(optional)Restrain sending http credentials on specific origin (scheme://host:port).
browserContext.setOffline()
Added in: v1.8 asyncArguments
Whether to emulate network being offline for the browser context.
INFO
Offline emulation affects HTTP requests, such as page navigations,
fetch()andXMLHttpRequest.WebSocket behavior depends on the browser and whether the connection is already established. Chromium and Firefox fail new WebSocket connections while offline, but do not close already-open connections. Chromium can defer incoming messages until the context goes back online, rather than lose them; Firefox can continue delivering messages while offline. WebKit can allow both new WebSocket connections and traffic on established connections while offline. Do not rely on offline emulation to test WebSocket message loss or connection closure.
Offline emulation does not affect WebRTC traffic: established
RTCPeerConnections keep sending and receiving media over UDP. To test WebRTC connection loss, interrupt the connection outside the browser, for example by stopping the TURN server or using an OS-level firewall.
browserContext.setStorageState()
Added in: v1.59 asyncClears the existing cookies, local storage, IndexedDB entries, origin private file system entries and virtual WebAuthn credentials, and sets the new storage state. When the storage state contains credentials, the virtual WebAuthn authenticator is installed (equivalent to credentials.install()), preventing all real authenticators from working in this context.
Usage
// Load storage state from a file and apply it to the context.
await context.setStorageState('state.json');Arguments
Learn more about storage state and auth.
Populates context with given storage state. This option can be used to initialize context with logged-in information obtained via
browserContext.storageState().cookiesArray<Object>Cookies to set for context
namestringvaluestringdomainstringDomain and path are required. For the cookie to apply to all subdomains as well, prefix domain with a dot, like this: ".example.com"
pathstringDomain and path are required
expiresfloatUnix time in seconds.
httpOnlybooleansecurebooleansameSite"Strict" | "Lax" | "None"sameSite flag
originsArray<Object>originstringlocalStorageArray<Object>localStorage to set for context
namestringvaluestring
browserContext.storageState()
Added in: v1.8 asyncReturns storage state for this browser context, contains current cookies, local storage snapshot, IndexedDB snapshot, origin private file system snapshot and virtual WebAuthn credentials.
Arguments
credentialsboolean(optional) Added in: v1.62Set to
trueto include the context's virtual WebAuthnbrowserContext.credentials(passkeys) in the storage state snapshot. The captured credentials carry their private keys and signature counters, so they can be re-seeded into a later context via thestorageStateoption orbrowserContext.setStorageState(). Note that restoring the storage state that contains credentials will automatically install the virtual WebAuthn authenticator (seecredentials.install()), and prevent all real authenticators from working in this context.indexedDBboolean(optional) Added in: v1.51Set to
trueto include IndexedDB in the storage state snapshot. If your application uses IndexedDB to store authentication tokens, like Firebase Authentication, enable this.opfsboolean(optional) Added in: v1.63Set to
trueto include the origin private file system in the storage state snapshot.INFO
OPFS is currently not supported in ephemeral WebKit contexts.
The file path to save the storage state to. If
pathis a relative path, then it is resolved relative to current working directory. If no path is provided, storage state is still returned, but won't be saved to the disk.
Returns
Promise<Object>
browserContext.unroute()
Added in: v1.8 asyncRemoves a route created with browserContext.route(). When handler is not specified, removes all routes for the url.
Arguments
urlstring | RegExp | URLPattern | function(URL): booleanA glob pattern, regex pattern, URL pattern, or predicate receiving [URL] used to register a routing with
browserContext.route().handlerfunction(Route, Request): Promise<any> | any(optional)Optional handler function used to register a routing with
browserContext.route().
browserContext.unrouteAll()
Added in: v1.41 asyncRemoves all routes created with browserContext.route() and browserContext.routeFromHAR().
Arguments
behavior"wait" | "ignoreErrors" | "default"(optional)Specifies whether to wait for already running handlers and what to do if they throw errors:
'default'- do not wait for current handler calls (if any) to finish, if unrouted handler throws, it may result in unhandled error'wait'- wait for current handler calls (if any) to finish'ignoreErrors'- do not wait for current handler calls (if any) to finish, all errors thrown by the handlers after unrouting are silently caught
browserContext.waitForEvent()
Added in: v1.8 asyncWaits for event to fire and passes its value into the predicate function. Returns when the predicate returns truthy value. Will throw an error if the context closes before the event is fired. Returns the event data value.
Usage
const pagePromise = context.waitForEvent('page');
await page.getByRole('button').click();
const page = await pagePromise;Arguments
Event name, same one would pass into
browserContext.on(event).optionsOrPredicatefunction() | Object(optional)Either a predicate that receives an event or an options object. Optional.
predicatefunction()Receives the event data and resolves to truthy value when the waiting should resolve.
timeoutfloat(optional)Maximum time to wait for in milliseconds. Defaults to
0- no timeout. The default value can be changed viaactionTimeoutoption in the config, or by using thebrowserContext.setDefaultTimeout()method.
predicatefunction()(optional)Receives the event data and resolves to truthy value when the waiting should resolve.
signalAbortSignal(optional) Added in: v1.62Allows to cancel the waiting using an
AbortSignal. If the signal is aborted, the waiting will be aborted and the operation will throw an error. Note that providing a signal does not disable the default timeout, which can be changed usingbrowserContext.setDefaultTimeout(); passtimeout: 0to disable the timeout entirely.
Returns
Promise<any>
Properties
browserContext.clock
Added in: v1.45Playwright has ability to mock clock and passage of time.
Type
Clock
browserContext.credentials
Added in: v1.61Virtual WebAuthn authenticator for this context. Lets tests seed credentials and intercept navigator.credentials.create() / navigator.credentials.get() ceremonies.
Type
Credentials
browserContext.debugger
Added in: v1.59Debugger allows to pause and resume the execution.
Type
Debugger
browserContext.request
Added in: v1.16API testing helper associated with this context. Requests made with this API will use context cookies.
Type
APIRequestContext
browserContext.tracing
Added in: v1.12Type
Tracing
Events
browserContext.on('close')
Added in: v1.8Emitted when Browser context gets closed. This might happen because of one of the following:
- Browser context is closed.
- Browser application is closed or crashed.
- The
browser.close()method was called.
Event data
BrowserContext
browserContext.on('console')
Added in: v1.34Emitted when JavaScript within the page calls one of console API methods, e.g. console.log or console.dir.
The arguments passed into console.log and the page are available on the ConsoleMessage event handler argument.
Usage
context.on('console', async msg => {
const values = [];
for (const arg of msg.args())
values.push(await arg.jsonValue());
console.log(...values);
});
await page.evaluate(() => console.log('hello', 5, { foo: 'bar' }));Event data
ConsoleMessage
browserContext.on('dialog')
Added in: v1.34Emitted when a JavaScript dialog appears, such as alert, prompt, confirm or beforeunload. Listener must either dialog.accept() or dialog.dismiss() the dialog - otherwise the page will freeze waiting for the dialog, and actions like click will never finish.
Usage
context.on('dialog', dialog => {
dialog.accept();
});INFO
When no page.on('dialog') or browserContext.on('dialog') listeners are present, all dialogs are automatically dismissed.
Event data
Dialog
browserContext.on('dialogClosed')
Added in: v1.63Emitted when a JavaScript dialog in any page belonging to this context has been closed, either by dialog.accept(), by dialog.dismiss(), or manually by the user in the headed browser.
Event data
Dialog
browserContext.on('download')
Added in: v1.60Emitted when attachment download started in any page belonging to this context. User can access basic file operations on downloaded content via the passed Download instance. See also page.on('download') to receive events about a specific page.
Event data
Download
browserContext.on('frameAttached')
Added in: v1.60Emitted when a frame is attached in any page belonging to this context. See also page.on('frameAttached') to receive events about a specific page.
Event data
Frame
browserContext.on('frameDetached')
Added in: v1.60Emitted when a frame is detached in any page belonging to this context. See also page.on('frameDetached') to receive events about a specific page.
Event data
Frame
browserContext.on('frameNavigated')
Added in: v1.60Emitted when a frame is navigated to a new url in any page belonging to this context. See also page.on('frameNavigated') to receive events about navigations in a specific page.
Event data
Frame
browserContext.on('page')
Added in: v1.8The event is emitted when a new Page is created in the BrowserContext. The page may still be loading. The event will also fire for popup pages. See also page.on('popup') to receive events about popups relevant to a specific page.
The earliest moment that page is available is when it has navigated to the initial url. For example, when opening a popup with window.open('http://example.com'), this event will fire when the network request to "http://example.com" is done and its response has started loading in the popup. If you would like to route/listen to this network request, use browserContext.route() and browserContext.on('request') respectively instead of similar methods on the Page.
const newPagePromise = context.waitForEvent('page');
await page.getByText('open new page').click();
const newPage = await newPagePromise;
console.log(await newPage.evaluate('location.href'));INFO
Use page.waitForLoadState() to wait until the page gets to a particular state (you should not need it in most cases).
Event data
Page
browserContext.on('pageClose')
Added in: v1.60Emitted when a page in this context is closed. See also page.on('close') to receive events about a specific page.
Event data
Page
browserContext.on('pageLoad')
Added in: v1.60Emitted when the JavaScript load event is dispatched in any page belonging to this context. See also page.on('load') to receive events about a specific page.
Event data
Page
browserContext.on('request')
Added in: v1.12Emitted when a request is issued from any pages created through this context. The [request] object is read-only. To only listen for requests from a particular page, use page.on('request').
In order to intercept and mutate requests, see browserContext.route() or page.route().
Event data
Request
browserContext.on('requestFailed')
Added in: v1.12Emitted when a request fails, for example by timing out. To only listen for failed requests from a particular page, use page.on('requestFailed').
INFO
HTTP Error responses, such as 404 or 503, are still successful responses from HTTP standpoint, so request will complete with browserContext.on('requestFinished') event and not with browserContext.on('requestFailed').
Event data
Request
browserContext.on('requestFinished')
Added in: v1.12Emitted when a request finishes successfully after downloading the response body. For a successful response, the sequence of events is request, response and requestfinished. To listen for successful requests from a particular page, use page.on('requestFinished').
Event data
Request
browserContext.on('response')
Added in: v1.12Emitted when [response] status and headers are received for a request. For a successful response, the sequence of events is request, response and requestfinished. To listen for response events from a particular page, use page.on('response').
Event data
Response
browserContext.on('serviceWorker')
Added in: v1.11INFO
Service workers are only supported on Chromium-based browsers.
Emitted when new service worker is created in the context.
Event data
Worker
browserContext.on('webError')
Added in: v1.38Emitted when exception is unhandled in any of the pages in this context. To listen for errors from a particular page, use page.on('pageError') instead.
Event data
WebError
Deprecated
browserContext.on('backgroundPage')
Added in: v1.11Deprecated
Background pages have been removed from Chromium together with Manifest V2 extensions.
This event is not emitted.
Event data
Page
browserContext.backgroundPages()
Added in: v1.11Deprecated
Background pages have been removed from Chromium together with Manifest V2 extensions.
Returns an empty list.
Returns
Array<Page>