microsoft · yury-s · Jun 5, 2026 · Jun 5, 2026
diff --git a/dotnet/docs/api/class-browsercontext.mdx b/dotnet/docs/api/class-browsercontext.mdx
@@ -1386,7 +1386,7 @@ BrowserContext.WebError += async (_, webError) => {};
 
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.11</font><x-search>browserContext.event BackgroundPage</x-search>
 
-:::warning Deprecated
+:::warning[Deprecated]
 
 Background pages have been removed from Chromium together with Manifest V2 extensions.
 
@@ -1410,7 +1410,7 @@ BrowserContext.BackgroundPage += async (_, page) => {};
 
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.11</font><x-search>browserContext.BackgroundPages</x-search>
 
-:::warning Deprecated
+:::warning[Deprecated]
 
 Background pages have been removed from Chromium together with Manifest V2 extensions.
 

diff --git a/dotnet/docs/api/class-elementhandle.mdx b/dotnet/docs/api/class-elementhandle.mdx
@@ -1428,7 +1428,7 @@ await ElementHandle.TextContentAsync();
 
 <font size="2" style={{position: "relative", top: "-20px"}}>Added before v1.9</font><x-search>elementHandle.TypeAsync</x-search>
 
-:::warning Deprecated
+:::warning[Deprecated]
 
 In most cases, you should use [Locator.FillAsync()](/api/class-locator.mdx#locator-fill) instead. You only need to press keys one by one if there is special keyboard handling on the page - in this case use [Locator.PressSequentiallyAsync()](/api/class-locator.mdx#locator-press-sequentially).
 

diff --git a/dotnet/docs/api/class-frame.mdx b/dotnet/docs/api/class-frame.mdx
@@ -2075,7 +2075,7 @@ await Frame.QuerySelectorAllAsync(selector);
 
 <font size="2" style={{position: "relative", top: "-20px"}}>Added before v1.9</font><x-search>frame.RunAndWaitForNavigationAsync</x-search>
 
-:::warning Deprecated
+:::warning[Deprecated]
 
 This method is inherently racy, please use [Frame.WaitForURLAsync()](/api/class-frame.mdx#frame-wait-for-url) instead.
 
@@ -2130,7 +2130,7 @@ Usage of the [History API](https://developer.mozilla.org/en-US/docs/Web/API/Hist
 
 <font size="2" style={{position: "relative", top: "-20px"}}>Added before v1.9</font><x-search>frame.WaitForNavigationAsync</x-search>
 
-:::warning Deprecated
+:::warning[Deprecated]
 
 This method is inherently racy, please use [Frame.WaitForURLAsync()](/api/class-frame.mdx#frame-wait-for-url) instead.
 
@@ -2486,7 +2486,7 @@ await Frame.TextContentAsync(selector, options);
 
 <font size="2" style={{position: "relative", top: "-20px"}}>Added before v1.9</font><x-search>frame.TypeAsync</x-search>
 
-:::warning Deprecated
+:::warning[Deprecated]
 
 In most cases, you should use [Locator.FillAsync()](/api/class-locator.mdx#locator-fill) instead. You only need to press keys one by one if there is special keyboard handling on the page - in this case use [Locator.PressSequentiallyAsync()](/api/class-locator.mdx#locator-press-sequentially).
 

diff --git a/dotnet/docs/api/class-framelocator.mdx b/dotnet/docs/api/class-framelocator.mdx
@@ -467,7 +467,7 @@ await Expect(locator).ToBeVisibleAsync();
 
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.17</font><x-search>frameLocator.First</x-search>
 
-:::warning Deprecated
+:::warning[Deprecated]
 
 Use [Locator.First](/api/class-locator.mdx#locator-first) followed by [Locator.ContentFrame](/api/class-locator.mdx#locator-content-frame) instead.
 
@@ -491,7 +491,7 @@ FrameLocator.First
 
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.17</font><x-search>frameLocator.Last</x-search>
 
-:::warning Deprecated
+:::warning[Deprecated]
 
 Use [Locator.Last](/api/class-locator.mdx#locator-last) followed by [Locator.ContentFrame](/api/class-locator.mdx#locator-content-frame) instead.
 
@@ -515,7 +515,7 @@ FrameLocator.Last
 
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.17</font><x-search>frameLocator.Nth</x-search>
 
-:::warning Deprecated
+:::warning[Deprecated]
 
 Use [Locator.Nth()](/api/class-locator.mdx#locator-nth) followed by [Locator.ContentFrame](/api/class-locator.mdx#locator-content-frame) instead.
 

diff --git a/dotnet/docs/api/class-locator.mdx b/dotnet/docs/api/class-locator.mdx
@@ -2588,7 +2588,7 @@ await Locator.ElementHandlesAsync();
 
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.14</font><x-search>locator.TypeAsync</x-search>
 
-:::warning Deprecated
+:::warning[Deprecated]
 
 In most cases, you should use [Locator.FillAsync()](/api/class-locator.mdx#locator-fill) instead. You only need to press keys one by one if there is special keyboard handling on the page - in this case use [Locator.PressSequentiallyAsync()](/api/class-locator.mdx#locator-press-sequentially).
 

diff --git a/dotnet/docs/api/class-page.mdx b/dotnet/docs/api/class-page.mdx
@@ -4447,7 +4447,7 @@ await Page.QuerySelectorAllAsync(selector);
 
 <font size="2" style={{position: "relative", top: "-20px"}}>Added before v1.9</font><x-search>page.RunAndWaitForNavigationAsync</x-search>
 
-:::warning Deprecated
+:::warning[Deprecated]
 
 This method is inherently racy, please use [Page.WaitForURLAsync()](/api/class-page.mdx#page-wait-for-url) instead.
 
@@ -4502,7 +4502,7 @@ Usage of the [History API](https://developer.mozilla.org/en-US/docs/Web/API/Hist
 
 <font size="2" style={{position: "relative", top: "-20px"}}>Added before v1.9</font><x-search>page.WaitForNavigationAsync</x-search>
 
-:::warning Deprecated
+:::warning[Deprecated]
 
 This method is inherently racy, please use [Page.WaitForURLAsync()](/api/class-page.mdx#page-wait-for-url) instead.
 
@@ -4858,7 +4858,7 @@ await Page.TextContentAsync(selector, options);
 
 <font size="2" style={{position: "relative", top: "-20px"}}>Added before v1.9</font><x-search>page.TypeAsync</x-search>
 
-:::warning Deprecated
+:::warning[Deprecated]
 
 In most cases, you should use [Locator.FillAsync()](/api/class-locator.mdx#locator-fill) instead. You only need to press keys one by one if there is special keyboard handling on the page - in this case use [Locator.PressSequentiallyAsync()](/api/class-locator.mdx#locator-press-sequentially).
 

diff --git a/java/docs/api/class-browsercontext.mdx b/java/docs/api/class-browsercontext.mdx
@@ -1368,7 +1368,7 @@ BrowserContext.onWebError(handler)
 
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.11</font><x-search>browserContext.onBackgroundPage(handler)</x-search>
 
-:::warning Deprecated
+:::warning[Deprecated]
 
 Background pages have been removed from Chromium together with Manifest V2 extensions.
 
@@ -1392,7 +1392,7 @@ BrowserContext.onBackgroundPage(handler)
 
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.11</font><x-search>browserContext.backgroundPages</x-search>
 
-:::warning Deprecated
+:::warning[Deprecated]
 
 Background pages have been removed from Chromium together with Manifest V2 extensions.
 

diff --git a/java/docs/api/class-elementhandle.mdx b/java/docs/api/class-elementhandle.mdx
@@ -1437,7 +1437,7 @@ ElementHandle.textContent();
 
 <font size="2" style={{position: "relative", top: "-20px"}}>Added before v1.9</font><x-search>elementHandle.type</x-search>
 
-:::warning Deprecated
+:::warning[Deprecated]
 
 In most cases, you should use [Locator.fill()](/api/class-locator.mdx#locator-fill) instead. You only need to press keys one by one if there is special keyboard handling on the page - in this case use [Locator.pressSequentially()](/api/class-locator.mdx#locator-press-sequentially).
 

diff --git a/java/docs/api/class-frame.mdx b/java/docs/api/class-frame.mdx
@@ -2406,7 +2406,7 @@ Frame.textContent(selector, options);
 
 <font size="2" style={{position: "relative", top: "-20px"}}>Added before v1.9</font><x-search>frame.type</x-search>
 
-:::warning Deprecated
+:::warning[Deprecated]
 
 In most cases, you should use [Locator.fill()](/api/class-locator.mdx#locator-fill) instead. You only need to press keys one by one if there is special keyboard handling on the page - in this case use [Locator.pressSequentially()](/api/class-locator.mdx#locator-press-sequentially).
 
@@ -2521,7 +2521,7 @@ Frame.uncheck(selector, options);
 
 <font size="2" style={{position: "relative", top: "-20px"}}>Added before v1.9</font><x-search>frame.waitForNavigation</x-search>
 
-:::warning Deprecated
+:::warning[Deprecated]
 
 This method is inherently racy, please use [Frame.waitForURL()](/api/class-frame.mdx#frame-wait-for-url) instead.
 

diff --git a/java/docs/api/class-framelocator.mdx b/java/docs/api/class-framelocator.mdx
@@ -466,7 +466,7 @@ assertThat(locator).isVisible();
 
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.17</font><x-search>frameLocator.first</x-search>
 
-:::warning Deprecated
+:::warning[Deprecated]
 
 Use [Locator.first()](/api/class-locator.mdx#locator-first) followed by [Locator.contentFrame()](/api/class-locator.mdx#locator-content-frame) instead.
 
@@ -490,7 +490,7 @@ FrameLocator.first();
 
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.17</font><x-search>frameLocator.last</x-search>
 
-:::warning Deprecated
+:::warning[Deprecated]
 
 Use [Locator.last()](/api/class-locator.mdx#locator-last) followed by [Locator.contentFrame()](/api/class-locator.mdx#locator-content-frame) instead.
 
@@ -514,7 +514,7 @@ FrameLocator.last();
 
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.17</font><x-search>frameLocator.nth</x-search>
 
-:::warning Deprecated
+:::warning[Deprecated]
 
 Use [Locator.nth()](/api/class-locator.mdx#locator-nth) followed by [Locator.contentFrame()](/api/class-locator.mdx#locator-content-frame) instead.
 

diff --git a/java/docs/api/class-locator.mdx b/java/docs/api/class-locator.mdx
@@ -2592,7 +2592,7 @@ Locator.elementHandles();
 
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.14</font><x-search>locator.type</x-search>
 
-:::warning Deprecated
+:::warning[Deprecated]
 
 In most cases, you should use [Locator.fill()](/api/class-locator.mdx#locator-fill) instead. You only need to press keys one by one if there is special keyboard handling on the page - in this case use [Locator.pressSequentially()](/api/class-locator.mdx#locator-press-sequentially).
 

diff --git a/java/docs/api/class-page.mdx b/java/docs/api/class-page.mdx
@@ -4642,7 +4642,7 @@ Page.textContent(selector, options);
 
 <font size="2" style={{position: "relative", top: "-20px"}}>Added before v1.9</font><x-search>page.type</x-search>
 
-:::warning Deprecated
+:::warning[Deprecated]
 
 In most cases, you should use [Locator.fill()](/api/class-locator.mdx#locator-fill) instead. You only need to press keys one by one if there is special keyboard handling on the page - in this case use [Locator.pressSequentially()](/api/class-locator.mdx#locator-press-sequentially).
 
@@ -4757,7 +4757,7 @@ Page.uncheck(selector, options);
 
 <font size="2" style={{position: "relative", top: "-20px"}}>Added before v1.9</font><x-search>page.waitForNavigation</x-search>
 
-:::warning Deprecated
+:::warning[Deprecated]
 
 This method is inherently racy, please use [Page.waitForURL()](/api/class-page.mdx#page-wait-for-url) instead.
 

diff --git a/nodejs/docs/api/class-browsercontext.mdx b/nodejs/docs/api/class-browsercontext.mdx
@@ -1052,6 +1052,9 @@ const page = await pagePromise;
   - `predicate` [function] *(optional)*<a aria-hidden="true" tabIndex="-1" class="list-anchor-link" id="browser-context-wait-for-event-option-predicate"/><a href="#browser-context-wait-for-event-option-predicate" class="list-anchor">#</a>
 
     Receives the event data and resolves to truthy value when the waiting should resolve.
+  - `signal` [AbortSignal] *(optional)* <font size="2">Added in: v1.61</font><a aria-hidden="true" tabIndex="-1" class="list-anchor-link" id="browser-context-wait-for-event-option-signal"/><a href="#browser-context-wait-for-event-option-signal" class="list-anchor">#</a>
+
+    Allows to cancel the waiting using an [`AbortSignal`](https://developer.mozilla.org/en-US/docs/Web/API/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; pass `timeout: 0` to disable the timeout entirely.
 
 **Returns**
 - [Promise]&lt;[Object]&gt;<a aria-hidden="true" tabIndex="-1" class="list-anchor-link" id="browser-context-wait-for-event-return"/><a href="#browser-context-wait-for-event-return" class="list-anchor">#</a>
@@ -1465,7 +1468,7 @@ browserContext.on('weberror', data => {});
 
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.11</font><x-search>browserContext.on('backgroundpage')</x-search>
 
-:::warning Deprecated
+:::warning[Deprecated]
 
 Background pages have been removed from Chromium together with Manifest V2 extensions.
 
@@ -1489,7 +1492,7 @@ browserContext.on('backgroundpage', data => {});
 
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.11</font><x-search>browserContext.backgroundPages</x-search>
 
-:::warning Deprecated
+:::warning[Deprecated]
 
 Background pages have been removed from Chromium together with Manifest V2 extensions.
 
@@ -1513,7 +1516,7 @@ browserContext.backgroundPages();
 
 <font size="2" style={{position: "relative", top: "-20px"}}>Added before v1.9</font><x-search>browserContext.setHTTPCredentials</x-search>
 
-:::warning Deprecated
+:::warning[Deprecated]
 
 Browsers may cache credentials after successful authentication. Create a new browser context instead.
 

diff --git a/nodejs/docs/api/class-elementhandle.mdx b/nodejs/docs/api/class-elementhandle.mdx
@@ -1441,7 +1441,7 @@ await elementHandle.textContent();
 
 <font size="2" style={{position: "relative", top: "-20px"}}>Added before v1.9</font><x-search>elementHandle.type</x-search>
 
-:::warning Deprecated
+:::warning[Deprecated]
 
 In most cases, you should use [locator.fill()](/api/class-locator.mdx#locator-fill) instead. You only need to press keys one by one if there is special keyboard handling on the page - in this case use [locator.pressSequentially()](/api/class-locator.mdx#locator-press-sequentially).
 

diff --git a/nodejs/docs/api/class-frame.mdx b/nodejs/docs/api/class-frame.mdx
@@ -1033,6 +1033,9 @@ await frame.waitForLoadState(); // Waits for 'load' state by default.
   * `'domcontentloaded'` - wait for the `DOMContentLoaded` event to be fired.
   * `'networkidle'` - **DISCOURAGED** wait until there are no network connections for at least `500` ms. Don't use this method for testing, rely on web assertions to assess readiness instead.
 - `options` [Object] *(optional)*
+  - `signal` [AbortSignal] *(optional)* <font size="2">Added in: v1.61</font><a aria-hidden="true" tabIndex="-1" class="list-anchor-link" id="frame-wait-for-load-state-option-signal"/><a href="#frame-wait-for-load-state-option-signal" class="list-anchor">#</a>
+
+    Allows to cancel the waiting using an [`AbortSignal`](https://developer.mozilla.org/en-US/docs/Web/API/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; pass `timeout: 0` to disable the timeout entirely.
   - `timeout` [number] *(optional)*<a aria-hidden="true" tabIndex="-1" class="list-anchor-link" id="frame-wait-for-load-state-option-timeout"/><a href="#frame-wait-for-load-state-option-timeout" class="list-anchor">#</a>
 
     Maximum operation time in milliseconds. Defaults to `0` - no timeout. The default value can be changed via `navigationTimeout` option in the config, or by using the [browserContext.setDefaultNavigationTimeout()](/api/class-browsercontext.mdx#browser-context-set-default-navigation-timeout), [browserContext.setDefaultTimeout()](/api/class-browsercontext.mdx#browser-context-set-default-timeout), [page.setDefaultNavigationTimeout()](/api/class-page.mdx#page-set-default-navigation-timeout) or [page.setDefaultTimeout()](/api/class-page.mdx#page-set-default-timeout) methods.
@@ -1060,6 +1063,9 @@ await frame.waitForURL('**/target.html');
 
   A glob pattern, regex pattern, URL pattern, or predicate receiving [URL] to match while waiting for the navigation. Note that if the parameter is a string without wildcard characters, the method will wait for navigation to URL that is exactly equal to the string.
 - `options` [Object] *(optional)*
+  - `signal` [AbortSignal] *(optional)* <font size="2">Added in: v1.61</font><a aria-hidden="true" tabIndex="-1" class="list-anchor-link" id="frame-wait-for-url-option-signal"/><a href="#frame-wait-for-url-option-signal" class="list-anchor">#</a>
+
+    Allows to cancel the waiting using an [`AbortSignal`](https://developer.mozilla.org/en-US/docs/Web/API/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; pass `timeout: 0` to disable the timeout entirely.
   - `timeout` [number] *(optional)*<a aria-hidden="true" tabIndex="-1" class="list-anchor-link" id="frame-wait-for-url-option-timeout"/><a href="#frame-wait-for-url-option-timeout" class="list-anchor">#</a>
 
     Maximum operation time in milliseconds. Defaults to `0` - no timeout. The default value can be changed via `navigationTimeout` option in the config, or by using the [browserContext.setDefaultNavigationTimeout()](/api/class-browsercontext.mdx#browser-context-set-default-navigation-timeout), [browserContext.setDefaultTimeout()](/api/class-browsercontext.mdx#browser-context-set-default-timeout), [page.setDefaultNavigationTimeout()](/api/class-page.mdx#page-set-default-navigation-timeout) or [page.setDefaultTimeout()](/api/class-page.mdx#page-set-default-timeout) methods.
@@ -2406,7 +2412,7 @@ await frame.textContent(selector, options);
 
 <font size="2" style={{position: "relative", top: "-20px"}}>Added before v1.9</font><x-search>frame.type</x-search>
 
-:::warning Deprecated
+:::warning[Deprecated]
 
 In most cases, you should use [locator.fill()](/api/class-locator.mdx#locator-fill) instead. You only need to press keys one by one if there is special keyboard handling on the page - in this case use [locator.pressSequentially()](/api/class-locator.mdx#locator-press-sequentially).
 
@@ -2521,7 +2527,7 @@ await frame.uncheck(selector, options);
 
 <font size="2" style={{position: "relative", top: "-20px"}}>Added before v1.9</font><x-search>frame.waitForNavigation</x-search>
 
-:::warning Deprecated
+:::warning[Deprecated]
 
 This method is inherently racy, please use [frame.waitForURL()](/api/class-frame.mdx#frame-wait-for-url) instead.
 
@@ -2547,6 +2553,9 @@ Usage of the [History API](https://developer.mozilla.org/en-US/docs/Web/API/Hist
 
 **Arguments**
 - `options` [Object] *(optional)*
+  - `signal` [AbortSignal] *(optional)* <font size="2">Added in: v1.61</font><a aria-hidden="true" tabIndex="-1" class="list-anchor-link" id="frame-wait-for-navigation-option-signal"/><a href="#frame-wait-for-navigation-option-signal" class="list-anchor">#</a>
+
+    Allows to cancel the waiting using an [`AbortSignal`](https://developer.mozilla.org/en-US/docs/Web/API/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; pass `timeout: 0` to disable the timeout entirely.
   - `timeout` [number] *(optional)*<a aria-hidden="true" tabIndex="-1" class="list-anchor-link" id="frame-wait-for-navigation-option-timeout"/><a href="#frame-wait-for-navigation-option-timeout" class="list-anchor">#</a>
 
     Maximum operation time in milliseconds. Defaults to `0` - no timeout. The default value can be changed via `navigationTimeout` option in the config, or by using the [browserContext.setDefaultNavigationTimeout()](/api/class-browsercontext.mdx#browser-context-set-default-navigation-timeout), [browserContext.setDefaultTimeout()](/api/class-browsercontext.mdx#browser-context-set-default-timeout), [page.setDefaultNavigationTimeout()](/api/class-page.mdx#page-set-default-navigation-timeout) or [page.setDefaultTimeout()](/api/class-page.mdx#page-set-default-timeout) methods.

diff --git a/nodejs/docs/api/class-framelocator.mdx b/nodejs/docs/api/class-framelocator.mdx
@@ -471,7 +471,7 @@ await expect(locator).toBeVisible();
 
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.17</font><x-search>frameLocator.first</x-search>
 
-:::warning Deprecated
+:::warning[Deprecated]
 
 Use [locator.first()](/api/class-locator.mdx#locator-first) followed by [locator.contentFrame()](/api/class-locator.mdx#locator-content-frame) instead.
 
@@ -495,7 +495,7 @@ frameLocator.first();
 
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.17</font><x-search>frameLocator.last</x-search>
 
-:::warning Deprecated
+:::warning[Deprecated]
 
 Use [locator.last()](/api/class-locator.mdx#locator-last) followed by [locator.contentFrame()](/api/class-locator.mdx#locator-content-frame) instead.
 
@@ -519,7 +519,7 @@ frameLocator.last();
 
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.17</font><x-search>frameLocator.nth</x-search>
 
-:::warning Deprecated
+:::warning[Deprecated]
 
 Use [locator.nth()](/api/class-locator.mdx#locator-nth) followed by [locator.contentFrame()](/api/class-locator.mdx#locator-content-frame) instead.