English · .NET
Appearance
English · .NET
Appearance
BrowserContexts 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.NewContextAsync() method. Non-persistent browser contexts don't write any browsing data to disk.
using var playwright = await Playwright.CreateAsync();
var browser = await playwright.Firefox.LaunchAsync(new() { Headless = false });
// Create a new incognito browser context
var context = await browser.NewContextAsync();
// Create a new page inside context.
var page = await context.NewPageAsync();
await page.GotoAsync("https://bing.com");
// Dispose context once it is no longer needed.
await context.CloseAsync();Adds cookies into this browser context. All pages within this context will have these cookies installed. Cookies can be obtained via BrowserContext.CookiesAsync().
Usage
await context.AddCookiesAsync(new[] { cookie1, cookie2 });Arguments
name string
value string
url string (optional)
Either url or both domain and path are required. Optional.
domain string (optional)
For the cookie to apply to all subdomains as well, prefix domain with a dot, like this: ".example.com". Either url or both domain and path are required. Optional.
path string (optional)
Either url or both domain and path are required. Optional.
expires float (optional)
Unix time in seconds. Optional.
httpOnly boolean (optional)
Optional.
secure boolean (optional)
Optional.
sameSite "Strict" | "Lax" | "None" (optional)
Optional.
partitionKey string (optional)
For partitioned third-party cookies (aka CHIPS), the partition key. Optional.
Adds a script which would be evaluated in one of the following scenarios:
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:
await Context.AddInitScriptAsync(scriptPath: "preload.js");INFO
The order of evaluation of multiple scripts installed via BrowserContext.AddInitScriptAsync() and Page.AddInitScriptAsync() is not defined.
Arguments
Returns
DisposableGets 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 | BrowserRemoves cookies from context. Accepts optional filter.
Usage
await context.ClearCookiesAsync();
await context.ClearCookiesAsync(new() { Name = "session-id" });
await context.ClearCookiesAsync(new() { Domain = "my-origin.com" });
await context.ClearCookiesAsync(new() { Path = "/api/v1" });
await context.ClearCookiesAsync(new() { Name = "session-id", Domain = "my-origin.com" });Arguments
domain string (optional) Added in: v1.43
Only removes cookies with the given domain.
domainRegex RegExp (optional) Added in: v1.43
Only removes cookies with the given domain.
domainString string (optional) Added in: v1.43
Only removes cookies with the given domain.
name string (optional) Added in: v1.43
Only removes cookies with the given name.
nameRegex RegExp (optional) Added in: v1.43
Only removes cookies with the given name.
nameString string (optional) Added in: v1.43
Only removes cookies with the given name.
path string (optional) Added in: v1.43
Only removes cookies with the given path.
pathRegex RegExp (optional) Added in: v1.43
Only removes cookies with the given path.
pathString string (optional) Added in: v1.43
Only removes cookies with the given path.
Clears all permission overrides for the browser context.
Usage
var context = await browser.NewContextAsync();
await context.GrantPermissionsAsync(new[] { "clipboard-read" });
// Alternatively, you can use the helper class ContextPermissions
// to specify the permissions...
// do stuff ...
await context.ClearPermissionsAsync();Closes the browser context. All the pages that belong to the browser context will be closed.
INFO
The default browser context cannot be closed.
Arguments
If no URLs are specified, this method returns all cookies. If URLs are specified, only cookies that affect those URLs are returned.
Arguments
Returns
Array<Object>The 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.ExposeBindingAsync() for page-only version.
Usage
An example of exposing page URL to all frames in all pages in the context:
using Microsoft.Playwright;
using var playwright = await Playwright.CreateAsync();
var browser = await playwright.Webkit.LaunchAsync(new() { Headless = false });
var context = await browser.NewContextAsync();
await context.ExposeBindingAsync("pageURL", source => source.Page.Url);
var page = await context.NewPageAsync();
await page.SetContentAsync("<script>\n" +
" async function onClick() {\n" +
" document.querySelector('div').textContent = await window.pageURL();\n" +
" }\n" +
"</script>\n" +
"<button onclick=\"onClick()\">Click me</button>\n" +
"<div></div>");
await page.GetByRole(AriaRole.Button).ClickAsync();Arguments
Name of the function on the window object.
Callback function that will be called in the Playwright's context.
Returns
DisposableThe 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.ExposeFunctionAsync() for page-only version.
Usage
An example of adding a sha256 function to all pages in the context:
using Microsoft.Playwright;
using System;
using System.Security.Cryptography;
using System.Threading.Tasks;
class BrowserContextExamples
{
public static async Task Main()
{
using var playwright = await Playwright.CreateAsync();
var browser = await playwright.Webkit.LaunchAsync(new() { Headless = false });
var context = await browser.NewContextAsync();
await context.ExposeFunctionAsync("sha256", (string input) =>
{
return Convert.ToBase64String(
SHA256.Create().ComputeHash(System.Text.Encoding.UTF8.GetBytes(input)));
});
var page = await context.NewPageAsync();
await page.SetContentAsync("<script>\n" +
" async function onClick() {\n" +
" document.querySelector('div').textContent = await window.sha256('PLAYWRIGHT');\n" +
" }\n" +
"</script>\n" +
"<button onclick=\"onClick()\">Click me</button>\n" +
"<div></div>");
await page.GetByRole(AriaRole.Button).ClickAsync();
Console.WriteLine(await page.TextContentAsync("div"));
}
}Arguments
Name of the function on the window object.
Callback function that will be called in the Playwright's context.
Returns
DisposableGrants 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".
Indicates that the browser context is in the process of closing or has already been closed.
Returns
booleanINFO
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 a Page or Frame type.
Returns
CDPSessionCreates a new page in the browser context.
Returns
PageReturns all open pages in the context.
Returns
Array<Page>Routing 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.RouteAsync() 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:
var context = await browser.NewContextAsync();
var page = await context.NewPageAsync();
await context.RouteAsync("**/*.{png,jpg,jpeg}", r => r.AbortAsync());
await page.GotoAsync("https://theverge.com");
await browser.CloseAsync();or the same snippet using a regex pattern instead:
var context = await browser.NewContextAsync();
var page = await context.NewPageAsync();
await context.RouteAsync(new Regex("(\\.png$)|(\\.jpg$)"), r => r.AbortAsync());
await page.GotoAsync("https://theverge.com");
await browser.CloseAsync();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 page.RouteAsync("/api/**", async r =>
{
if (r.Request.PostData.Contains("my-string"))
await r.FulfillAsync(new() { Body = "mocked-data" });
else
await r.ContinueAsync();
});Page routes (set up with Page.RouteAsync()) take precedence over browser context routes when request matches both handlers.
To remove a route with its handler you can use BrowserContext.UnrouteAsync().
INFO
Enabling routing disables http cache.
Arguments
url string | RegExp | function(URL): boolean
A glob pattern, regex pattern, or predicate that receives a [URL] to match during routing. If baseURL is set in the context options and the provided URL is a string that does not start with *, it is resolved using the new URL() constructor.
handler function to route the request.
Returns
DisposableIf 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 path is a relative path, then it is resolved relative to the current working directory.
notFound "abort" | "fallback" (optional)
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.CloseAsync() is called.
updateContent "embed" | "attach" (optional) Added in: v1.32
Optional setting to control resource content management. If attach is specified, resources are persisted as separate files or entries in the ZIP archive. If embed is specified, content is stored inline the HAR file.
updateMode "full" | "minimal" (optional) Added in: v1.32
When 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 to minimal.
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.
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.
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.
This 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.RouteWebSocketAsync("/ws", ws => {
var server = ws.ConnectToServer();
ws.OnMessage(frame => {
if (frame.Text == "to-be-blocked")
return;
server.Send(frame.Text);
});
});Arguments
url string | RegExp | function(URL): boolean
Only WebSockets with the url matching this pattern will be routed. A string pattern can be relative to the baseURL context option.
handler function(WebSocketRoute)
Handler function to route the WebSocket.
Performs action and waits for a ConsoleMessage to be logged by in the pages in the context. If predicate is provided, it passes ConsoleMessage value into the predicate function and waits for predicate(message) to return a truthy value. Will throw an error if the page is closed before the BrowserContext.Console event is fired.
Arguments
Action that triggers the event.
predicate function(ConsoleMessage): boolean (optional)
Receives the ConsoleMessage object and resolves to truthy value when the waiting should resolve.
Maximum time to wait for in milliseconds. Defaults to 30000 (30 seconds). Pass 0 to disable timeout. The default value can be changed by using the BrowserContext.SetDefaultTimeout().
Returns
ConsoleMessagePerforms action and waits for a new Page to be created in the context. If predicate is provided, it passes Page value into the predicate function and waits for predicate(event) to return a truthy value. Will throw an error if the context closes before new Page is created.
Arguments
action Func<Task> Added in: v1.12
Action that triggers the event.
predicate function(Page): boolean (optional)
Receives the Page object and resolves to truthy value when the waiting should resolve.
Maximum time to wait for in milliseconds. Defaults to 30000 (30 seconds). Pass 0 to disable timeout. The default value can be changed by using the BrowserContext.SetDefaultTimeout().
Returns
PageThis setting will change the default maximum navigation time for the following methods and related shortcuts:
Page.GoBackAsync()Page.GoForwardAsync()Page.GotoAsync()Page.ReloadAsync()Page.SetContentAsync()Page.RunAndWaitForNavigationAsync()INFO
Page.SetDefaultNavigationTimeout() and Page.SetDefaultTimeout() take priority over BrowserContext.SetDefaultNavigationTimeout().
Arguments
This 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
The 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.SetExtraHTTPHeadersAsync(). If page overrides a particular header, page-specific header value will be used instead of the browser context header value.
INFO
BrowserContext.SetExtraHTTPHeadersAsync() does not guarantee the order of headers in the outgoing requests.
Arguments
headers Object<string, string>
An object containing additional HTTP headers to be sent with every request. All header values must be strings.
Sets the context's geolocation. Passing null or undefined emulates position unavailable.
Usage
await context.SetGeolocationAsync(new Geolocation()
{
Latitude = 59.95f,
Longitude = 30.31667f
});INFO
Consider using BrowserContext.GrantPermissionsAsync() to grant permissions for the browser context pages to read its geolocation.
Arguments
latitude float
Latitude between -90 and 90.
longitude float
Longitude between -180 and 180.
accuracy float (optional)
Non-negative accuracy value. Defaults to 0.
Arguments
Whether to emulate network being offline for the browser context.
INFO
Offline emulation affects HTTP requests, such as page navigations, fetch() and XMLHttpRequest.
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.
Clears 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.InstallAsync()), preventing all real authenticators from working in this context.
Usage
// Load storage state from a file and apply it to the context.
await context.SetStorageStateAsync("state.json");Arguments
Populates context with given storage state. This option can be used to initialize context with logged-in information obtained via BrowserContext.StorageStateAsync(). Path to the file with saved storage state.
Returns storage state for this browser context, contains current cookies, local storage snapshot, IndexedDB snapshot, origin private file system snapshot and virtual WebAuthn credentials.
Arguments
credentials boolean (optional) Added in: v1.62
Set to true to include the context's virtual WebAuthn BrowserContext.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 the storageState option or BrowserContext.SetStorageStateAsync(). Note that restoring the storage state that contains credentials will automatically install the virtual WebAuthn authenticator (see Credentials.InstallAsync()), and prevent all real authenticators from working in this context.
indexedDB boolean (optional) Added in: v1.51
Set to true to include IndexedDB in the storage state snapshot. If your application uses IndexedDB to store authentication tokens, like Firebase Authentication, enable this.
opfs boolean (optional) Added in: v1.63
Set to true to 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 path is 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
stringRemoves a route created with BrowserContext.RouteAsync(). When handler is not specified, removes all routes for the url.
Arguments
url string | RegExp | function(URL): boolean
A glob pattern, regex pattern, or predicate receiving [URL] used to register a routing with BrowserContext.RouteAsync().
handler function(Route) (optional)
Optional handler function used to register a routing with BrowserContext.RouteAsync().
Removes all routes created with BrowserContext.RouteAsync() and BrowserContext.RouteFromHARAsync().
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 caughtAPI testing helper associated with this context. Requests made with this API will use context cookies.
Type
APIRequestContextPlaywright has ability to mock clock and passage of time.
Type
ClockVirtual WebAuthn authenticator for this context. Lets tests seed credentials and intercept navigator.credentials.create() / navigator.credentials.get() ceremonies.
Type
CredentialsDebugger allows to pause and resume the execution.
Type
DebuggerType
TracingEmitted when Browser context gets closed. This might happen because of one of the following:
Browser.CloseAsync() method was called.Event data
BrowserContextEmitted 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.Console += async (_, msg) =>
{
foreach (var arg in msg.Args)
Console.WriteLine(await arg.JsonValueAsync<object>());
};
await page.EvaluateAsync("console.log('hello', 5, { foo: 'bar' })");Event data
ConsoleMessageEmitted when a JavaScript dialog appears, such as alert, prompt, confirm or beforeunload. Listener must either Dialog.AcceptAsync() or Dialog.DismissAsync() the dialog - otherwise the page will freeze waiting for the dialog, and actions like click will never finish.
Usage
Context.Dialog += async (_, dialog) =>
{
await dialog.AcceptAsync();
};INFO
When no Page.Dialog or BrowserContext.Dialog listeners are present, all dialogs are automatically dismissed.
Event data
DialogEmitted when a JavaScript dialog in any page belonging to this context has been closed, either by Dialog.AcceptAsync(), by Dialog.DismissAsync(), or manually by the user in the headed browser.
Event data
DialogEmitted 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.Download to receive events about a specific page.
Event data
DownloadEmitted when a frame is attached in any page belonging to this context. See also Page.FrameAttached to receive events about a specific page.
Event data
FrameEmitted when a frame is detached in any page belonging to this context. See also Page.FrameDetached to receive events about a specific page.
Event data
FrameEmitted when a frame is navigated to a new url in any page belonging to this context. See also Page.FrameNavigated to receive events about navigations in a specific page.
Event data
FrameThe 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.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.RouteAsync() and BrowserContext.Request respectively instead of similar methods on the Page.
var popup = await context.RunAndWaitForPageAsync(async =>
{
await page.GetByText("open new page").ClickAsync();
});
Console.WriteLine(await popup.EvaluateAsync<string>("location.href"));INFO
Use Page.WaitForLoadStateAsync() to wait until the page gets to a particular state (you should not need it in most cases).
Event data
PageEmitted when a page in this context is closed. See also Page.Close to receive events about a specific page.
Event data
PageEmitted when the JavaScript load event is dispatched in any page belonging to this context. See also Page.Load to receive events about a specific page.
Event data
PageEmitted 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.Request.
In order to intercept and mutate requests, see BrowserContext.RouteAsync() or Page.RouteAsync().
Event data
RequestEmitted when a request fails, for example by timing out. To only listen for failed requests from a particular page, use Page.RequestFailed.
INFO
HTTP Error responses, such as 404 or 503, are still successful responses from HTTP standpoint, so request will complete with BrowserContext.RequestFinished event and not with BrowserContext.RequestFailed.
Event data
RequestEmitted 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.RequestFinished.
Event data
RequestEmitted 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.Response.
Event data
ResponseEmitted when exception is unhandled in any of the pages in this context. To listen for errors from a particular page, use Page.PageError instead.
Event data
WebErrorDeprecated
Background pages have been removed from Chromium together with Manifest V2 extensions.
This event is not emitted.
Event data
PageDeprecated
Background pages have been removed from Chromium together with Manifest V2 extensions.
Returns an empty list.
Returns
Array<Page>