feat(roll): roll to 1.62 Playwright

dotnet/versioned_docs/version-stable/api/class-apiresponse.mdx

@@ -229,6 +229,50 @@ await ApiResponse.TextAsync();
 
 ---
 
+### Timing {/* #api-response-timing */}
+
+<font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.62</font><x-search>apiResponse.Timing</x-search>
+
+Returns resource timing information for given response. For redirected requests, returns the information for the last request in the redirect chain. When the response is served [from the HAR file](../mock.mdx#replaying-from-har), timing information is not available and all the values are -1. Find more information at [Resource Timing API](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceResourceTiming).
+
+**Usage**
+
+```csharp
+ApiResponse.Timing
+```
+
+**Returns**
+- Timing<a aria-hidden="true" tabIndex="-1" class="list-anchor-link" id="api-response-timing-return"/><a href="#api-response-timing-return" class="list-anchor">#</a>
+  - `startTime` [float]
+
+    Request start time in milliseconds elapsed since January 1, 1970 00:00:00 UTC
+  - `domainLookupStart` [float]
+
+    Time immediately before the client starts the domain name lookup for the resource. The value is given in milliseconds relative to `startTime`, -1 if not available.
+  - `domainLookupEnd` [float]
+
+    Time immediately after the client ends the domain name lookup for the resource. The value is given in milliseconds relative to `startTime`, -1 if not available.
+  - `connectStart` [float]
+
+    Time immediately before the client starts establishing the connection to the server to retrieve the resource. The value is given in milliseconds relative to `startTime`, -1 if not available.
+  - `secureConnectionStart` [float]
+
+    Time immediately before the client starts the handshake process to secure the current connection. The value is given in milliseconds relative to `startTime`, -1 if not available.
+  - `connectEnd` [float]
+
+    Time immediately after the client establishes the connection to the server to retrieve the resource. The value is given in milliseconds relative to `startTime`, -1 if not available.
+  - `requestStart` [float]
+
+    Time immediately before the client starts requesting the resource from the server, cache, or local resource. The value is given in milliseconds relative to `startTime`, -1 if not available.
+  - `responseStart` [float]
+
+    Time immediately after the client receives the first byte of the response from the server, cache, or local resource. The value is given in milliseconds relative to `startTime`, -1 if not available.
+  - `responseEnd` [float]
+
+    Time immediately after the client receives the last byte of the resource or immediately before the transport connection is closed, whichever comes first. The value is given in milliseconds relative to `startTime`, -1 if not available.
+
+---
+
 ### Url {/* #api-response-url */}
 
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.16</font><x-search>apiResponse.Url</x-search>

dotnet/versioned_docs/version-stable/api/class-browsercontext.mdx

@@ -903,7 +903,7 @@ await BrowserContext.SetOfflineAsync(offline);
 
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.59</font><x-search>browserContext.SetStorageStateAsync</x-search>
 
-Clears the existing cookies, local storage and IndexedDB entries for all origins and sets the new storage state.
+Clears the existing cookies, local storage, IndexedDB 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()](/api/class-credentials.mdx#credentials-install)), preventing all real authenticators from working in this context.
 
 **Usage**
 
@@ -926,7 +926,7 @@ await context.SetStorageStateAsync("state.json");
 
 <font size="2" style={{position: "relative", top: "-20px"}}>Added before v1.9</font><x-search>browserContext.StorageStateAsync</x-search>
 
-Returns storage state for this browser context, contains current cookies, local storage snapshot and IndexedDB snapshot.
+Returns storage state for this browser context, contains current cookies, local storage snapshot, IndexedDB snapshot and virtual WebAuthn credentials.
 
 **Usage**
 
@@ -936,6 +936,9 @@ await BrowserContext.StorageStateAsync(options);
 
 **Arguments**
 - `options` `BrowserContextStorageStateOptions?` *(optional)*
+  - `Credentials` [bool]? *(optional)* <font size="2">Added in: v1.61</font><a aria-hidden="true" tabIndex="-1" class="list-anchor-link" id="browser-context-storage-state-option-credentials"/><a href="#browser-context-storage-state-option-credentials" class="list-anchor">#</a>
+
+    Set to `true` to include the context's virtual WebAuthn [BrowserContext.Credentials](/api/class-browsercontext.mdx#browser-context-credentials) (passkeys) in the storage state snapshot. The captured credentials carry their private keys, so they can be re-seeded into a later context via the [StorageState](/api/class-browser.mdx#browser-new-context-option-storage-state) option or [BrowserContext.SetStorageStateAsync()](/api/class-browsercontext.mdx#browser-context-set-storage-state). Note that restoring the storage state that contains credentials will automatically install the virtual WebAuthn authenticator (see [Credentials.InstallAsync()](/api/class-credentials.mdx#credentials-install)), and prevent all real authenticators from working in this context.
   - `IndexedDB` [bool]? *(optional)* <font size="2">Added in: v1.51</font><a aria-hidden="true" tabIndex="-1" class="list-anchor-link" id="browser-context-storage-state-option-indexed-db"/><a href="#browser-context-storage-state-option-indexed-db" class="list-anchor">#</a>
 
     Set to `true` to include [IndexedDB](https://developer.mozilla.org/en-US/docs/Web/API/IndexedDB_API) in the storage state snapshot. If your application uses IndexedDB to store authentication tokens, like Firebase Authentication, enable this.

dotnet/versioned_docs/version-stable/api/class-browsertype.mdx

@@ -100,6 +100,10 @@ Connecting over the Chrome DevTools Protocol is only supported for Chromium-base
 This connection is significantly lower fidelity than the Playwright protocol connection via [BrowserType.ConnectAsync()](/api/class-browsertype.mdx#browser-type-connect). If you are experiencing issues or attempting to use advanced functionality, you probably want to use [BrowserType.ConnectAsync()](/api/class-browsertype.mdx#browser-type-connect).
 :::
 
+:::warning
+Playwright maintains a curated list of arguments for launching the browser. If you launch the browser without Playwright and do not pass the exact same arguments, some of Playwright functionality may be broken upon connecting to the browser.
+:::
+
 **Usage**
 
 ```csharp

dotnet/versioned_docs/version-stable/api/class-credentials.mdx

@@ -9,7 +9,7 @@ import HTMLCard from '@site/src/components/HTMLCard';
 
 `Credentials` is a virtual WebAuthn authenticator scoped to a [BrowserContext]. It lets tests register passkeys and answer `navigator.credentials.create()` / `navigator.credentials.get()` ceremonies in the page, without a real authenticator or hardware security key.
 
-There are two common ways to use it:
+There are three common ways to use it:
 
 **Usage: seed a known credential**
 
@@ -31,7 +31,7 @@ await page.GotoAsync("https://example.com/login");
 // The page's navigator.credentials.get() is answered with the seeded passkey.
 ```
 
-**Usage: capture a passkey, then reuse it**
+**Usage: capture a credential, then reuse it**
 
 ```csharp
 // setup test: let the app register a passkey, then save it.
@@ -66,6 +66,10 @@ await page.GotoAsync("https://example.com/login");
 // navigator.credentials.get() resolves the captured passkey — already signed in.
 ```
 
+**Usage: save credentials in the storage state, restore later**
+
+See [authentication guide](../auth.mdx) for examples of using saving and resotring the storage state.
+
 **Defaults**