microsoft · agg23 · Oct 3, 2025 · Oct 3, 2025
diff --git a/dotnet/docs/actionability.mdx b/dotnet/docs/actionability.mdx
@@ -5,7 +5,6 @@ title: "Auto-waiting"
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import HTMLCard from '@site/src/components/HTMLCard';
-import ProgressiveImage from '@theme/ProgressiveImage';
 
 ## Introduction
 

diff --git a/dotnet/docs/api-testing.mdx b/dotnet/docs/api-testing.mdx
@@ -5,7 +5,6 @@ title: "API testing"
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import HTMLCard from '@site/src/components/HTMLCard';
-import ProgressiveImage from '@theme/ProgressiveImage';
 
 ## Introduction
 

diff --git a/dotnet/docs/api/class-accessibility.mdx b/dotnet/docs/api/class-accessibility.mdx
@@ -5,7 +5,6 @@ title: "Accessibility"
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import HTMLCard from '@site/src/components/HTMLCard';
-import ProgressiveImage from '@theme/ProgressiveImage';
 
 
 :::warning[Deprecated]

diff --git a/dotnet/docs/api/class-apirequest.mdx b/dotnet/docs/api/class-apirequest.mdx
@@ -5,7 +5,6 @@ title: "APIRequest"
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import HTMLCard from '@site/src/components/HTMLCard';
-import ProgressiveImage from '@theme/ProgressiveImage';
 
 
 Exposes API that can be used for the Web API testing. This class is used for creating [APIRequestContext] instance which in turn can be used for sending web requests. An instance of this class can be obtained via [Playwright.APIRequest](/api/class-playwright.mdx#playwright-request). For more information see [APIRequestContext].

diff --git a/dotnet/docs/api/class-apirequestcontext.mdx b/dotnet/docs/api/class-apirequestcontext.mdx
@@ -5,7 +5,6 @@ title: "APIRequestContext"
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import HTMLCard from '@site/src/components/HTMLCard';
-import ProgressiveImage from '@theme/ProgressiveImage';
 
 
 This API is used for the Web API testing. You can use it to trigger API endpoints, configure micro-services, prepare environment or the service to your e2e test.

diff --git a/dotnet/docs/api/class-apiresponse.mdx b/dotnet/docs/api/class-apiresponse.mdx
@@ -5,7 +5,6 @@ title: "APIResponse"
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import HTMLCard from '@site/src/components/HTMLCard';
-import ProgressiveImage from '@theme/ProgressiveImage';
 
 
 [APIResponse] class represents responses returned by [ApiRequestContext.GetAsync()](/api/class-apirequestcontext.mdx#api-request-context-get) and similar methods.

diff --git a/dotnet/docs/api/class-apiresponseassertions.mdx b/dotnet/docs/api/class-apiresponseassertions.mdx
@@ -5,7 +5,6 @@ title: "APIResponseAssertions"
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import HTMLCard from '@site/src/components/HTMLCard';
-import ProgressiveImage from '@theme/ProgressiveImage';
 
 
 The [APIResponseAssertions] class provides assertion methods that can be used to make assertions about the [APIResponse] in the tests.

diff --git a/dotnet/docs/api/class-browser.mdx b/dotnet/docs/api/class-browser.mdx
@@ -5,7 +5,6 @@ title: "Browser"
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import HTMLCard from '@site/src/components/HTMLCard';
-import ProgressiveImage from '@theme/ProgressiveImage';
 
 
 A Browser is created via [BrowserType.LaunchAsync()](/api/class-browsertype.mdx#browser-type-launch). An example of using a [Browser] to create a [Page]:

diff --git a/dotnet/docs/api/class-browsercontext.mdx b/dotnet/docs/api/class-browsercontext.mdx
@@ -5,7 +5,6 @@ title: "BrowserContext"
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import HTMLCard from '@site/src/components/HTMLCard';
-import ProgressiveImage from '@theme/ProgressiveImage';
 
 
 BrowserContexts provide a way to operate multiple independent browser sessions.

diff --git a/dotnet/docs/api/class-browsertype.mdx b/dotnet/docs/api/class-browsertype.mdx
@@ -5,7 +5,6 @@ title: "BrowserType"
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import HTMLCard from '@site/src/components/HTMLCard';
-import ProgressiveImage from '@theme/ProgressiveImage';
 
 
 BrowserType provides methods to launch a specific browser instance or connect to an existing one. The following is a typical example of using Playwright to drive automation:

diff --git a/dotnet/docs/api/class-cdpsession.mdx b/dotnet/docs/api/class-cdpsession.mdx
@@ -5,7 +5,6 @@ title: "CDPSession"
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import HTMLCard from '@site/src/components/HTMLCard';
-import ProgressiveImage from '@theme/ProgressiveImage';
 
 
 The `CDPSession` instances are used to talk raw Chrome Devtools Protocol:

diff --git a/dotnet/docs/api/class-cdpsessionevent.mdx b/dotnet/docs/api/class-cdpsessionevent.mdx
@@ -5,7 +5,6 @@ title: "CDPSessionEvent"
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import HTMLCard from '@site/src/components/HTMLCard';
-import ProgressiveImage from '@theme/ProgressiveImage';
 
 
 [CDPSessionEvent] objects are returned by page via the [CdpSession.Event()](/api/class-cdpsession.mdx#cdp-session-event) method.

diff --git a/dotnet/docs/api/class-clock.mdx b/dotnet/docs/api/class-clock.mdx
@@ -5,7 +5,6 @@ title: "Clock"
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import HTMLCard from '@site/src/components/HTMLCard';
-import ProgressiveImage from '@theme/ProgressiveImage';
 
 
 Accurately simulating time-dependent behavior is essential for verifying the correctness of applications. Learn more about [clock emulation](../clock.mdx).

diff --git a/dotnet/docs/api/class-consolemessage.mdx b/dotnet/docs/api/class-consolemessage.mdx
@@ -5,7 +5,6 @@ title: "ConsoleMessage"
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import HTMLCard from '@site/src/components/HTMLCard';
-import ProgressiveImage from '@theme/ProgressiveImage';
 
 
 [ConsoleMessage] objects are dispatched by page via the [Page.Console](/api/class-page.mdx#page-event-console) event. For each console message logged in the page there will be corresponding event in the Playwright context.

diff --git a/dotnet/docs/api/class-dialog.mdx b/dotnet/docs/api/class-dialog.mdx
@@ -5,7 +5,6 @@ title: "Dialog"
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import HTMLCard from '@site/src/components/HTMLCard';
-import ProgressiveImage from '@theme/ProgressiveImage';
 
 
 [Dialog] objects are dispatched by page via the [Page.Dialog](/api/class-page.mdx#page-event-dialog) event.

diff --git a/dotnet/docs/api/class-download.mdx b/dotnet/docs/api/class-download.mdx
@@ -5,7 +5,6 @@ title: "Download"
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import HTMLCard from '@site/src/components/HTMLCard';
-import ProgressiveImage from '@theme/ProgressiveImage';
 
 
 [Download] objects are dispatched by page via the [Page.Download](/api/class-page.mdx#page-event-download) event.

diff --git a/dotnet/docs/api/class-elementhandle.mdx b/dotnet/docs/api/class-elementhandle.mdx
@@ -5,7 +5,6 @@ title: "ElementHandle"
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import HTMLCard from '@site/src/components/HTMLCard';
-import ProgressiveImage from '@theme/ProgressiveImage';
 
 * extends: [JSHandle]
 

diff --git a/dotnet/docs/api/class-filechooser.mdx b/dotnet/docs/api/class-filechooser.mdx
@@ -5,7 +5,6 @@ title: "FileChooser"
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import HTMLCard from '@site/src/components/HTMLCard';
-import ProgressiveImage from '@theme/ProgressiveImage';
 
 
 [FileChooser] objects are dispatched by the page in the [Page.FileChooser](/api/class-page.mdx#page-event-file-chooser) event.

diff --git a/dotnet/docs/api/class-formdata.mdx b/dotnet/docs/api/class-formdata.mdx
@@ -5,7 +5,6 @@ title: "FormData"
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import HTMLCard from '@site/src/components/HTMLCard';
-import ProgressiveImage from '@theme/ProgressiveImage';
 
 
 The [FormData] is used create form data that is sent via [APIRequestContext].

diff --git a/dotnet/docs/api/class-frame.mdx b/dotnet/docs/api/class-frame.mdx
@@ -5,7 +5,6 @@ title: "Frame"
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import HTMLCard from '@site/src/components/HTMLCard';
-import ProgressiveImage from '@theme/ProgressiveImage';
 
 
 At every point of time, page exposes its current frame tree via the [Page.MainFrame](/api/class-page.mdx#page-main-frame) and [Frame.ChildFrames](/api/class-frame.mdx#frame-child-frames) methods.

diff --git a/dotnet/docs/api/class-framelocator.mdx b/dotnet/docs/api/class-framelocator.mdx
@@ -5,7 +5,6 @@ title: "FrameLocator"
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import HTMLCard from '@site/src/components/HTMLCard';
-import ProgressiveImage from '@theme/ProgressiveImage';
 
 
 FrameLocator represents a view to the `iframe` on the page. It captures the logic sufficient to retrieve the `iframe` and locate elements in that iframe. FrameLocator can be created with either [Locator.ContentFrame](/api/class-locator.mdx#locator-content-frame), [Page.FrameLocator()](/api/class-page.mdx#page-frame-locator) or [Locator.FrameLocator()](/api/class-locator.mdx#locator-frame-locator) method.

diff --git a/dotnet/docs/api/class-jshandle.mdx b/dotnet/docs/api/class-jshandle.mdx
@@ -5,7 +5,6 @@ title: "JSHandle"
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import HTMLCard from '@site/src/components/HTMLCard';
-import ProgressiveImage from '@theme/ProgressiveImage';
 
 
 JSHandle represents an in-page JavaScript object. JSHandles can be created with the [Page.EvaluateHandleAsync()](/api/class-page.mdx#page-evaluate-handle) method.

diff --git a/dotnet/docs/api/class-keyboard.mdx b/dotnet/docs/api/class-keyboard.mdx
@@ -5,7 +5,6 @@ title: "Keyboard"
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import HTMLCard from '@site/src/components/HTMLCard';
-import ProgressiveImage from '@theme/ProgressiveImage';
 
 
 Keyboard provides an api for managing a virtual keyboard. The high level api is [Keyboard.TypeAsync()](/api/class-keyboard.mdx#keyboard-type), which takes raw characters and generates proper `keydown`, `keypress`/`input`, and `keyup` events on your page.

diff --git a/dotnet/docs/api/class-locator.mdx b/dotnet/docs/api/class-locator.mdx
@@ -5,7 +5,6 @@ title: "Locator"
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import HTMLCard from '@site/src/components/HTMLCard';
-import ProgressiveImage from '@theme/ProgressiveImage';
 
 
 Locators are the central piece of Playwright's auto-waiting and retry-ability. In a nutshell, locators represent a way to find element(s) on the page at any moment. A locator can be created with the [Page.Locator()](/api/class-page.mdx#page-locator) method.

diff --git a/dotnet/docs/api/class-locatorassertions.mdx b/dotnet/docs/api/class-locatorassertions.mdx
@@ -5,7 +5,6 @@ title: "LocatorAssertions"
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import HTMLCard from '@site/src/components/HTMLCard';
-import ProgressiveImage from '@theme/ProgressiveImage';
 
 
 The [LocatorAssertions] class provides assertion methods that can be used to make assertions about the [Locator] state in the tests.

diff --git a/dotnet/docs/api/class-mouse.mdx b/dotnet/docs/api/class-mouse.mdx
@@ -5,7 +5,6 @@ title: "Mouse"
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import HTMLCard from '@site/src/components/HTMLCard';
-import ProgressiveImage from '@theme/ProgressiveImage';
 
 
 The Mouse class operates in main-frame CSS pixels relative to the top-left corner of the viewport.

diff --git a/dotnet/docs/api/class-page.mdx b/dotnet/docs/api/class-page.mdx
@@ -5,7 +5,6 @@ title: "Page"
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import HTMLCard from '@site/src/components/HTMLCard';
-import ProgressiveImage from '@theme/ProgressiveImage';
 
 
 Page provides methods to interact with a single tab in a [Browser], or an [extension background page](https://developer.chrome.com/extensions/background_pages) in Chromium. One [Browser] instance might have multiple [Page] instances.

diff --git a/dotnet/docs/api/class-pageassertions.mdx b/dotnet/docs/api/class-pageassertions.mdx
@@ -5,7 +5,6 @@ title: "PageAssertions"
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import HTMLCard from '@site/src/components/HTMLCard';
-import ProgressiveImage from '@theme/ProgressiveImage';
 
 
 The [PageAssertions] class provides assertion methods that can be used to make assertions about the [Page] state in the tests.

diff --git a/dotnet/docs/api/class-playwright.mdx b/dotnet/docs/api/class-playwright.mdx
@@ -5,7 +5,6 @@ title: "Playwright"
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import HTMLCard from '@site/src/components/HTMLCard';
-import ProgressiveImage from '@theme/ProgressiveImage';
 
 
 Playwright module provides a method to launch a browser instance. The following is a typical example of using Playwright to drive automation:

diff --git a/dotnet/docs/api/class-playwrightassertions.mdx b/dotnet/docs/api/class-playwrightassertions.mdx
@@ -5,7 +5,6 @@ title: "PlaywrightAssertions"
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import HTMLCard from '@site/src/components/HTMLCard';
-import ProgressiveImage from '@theme/ProgressiveImage';
 
 
 Playwright gives you Web-First Assertions with convenience methods for creating assertions that will wait and retry until the expected condition is met.

diff --git a/dotnet/docs/api/class-request.mdx b/dotnet/docs/api/class-request.mdx
@@ -5,7 +5,6 @@ title: "Request"
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import HTMLCard from '@site/src/components/HTMLCard';
-import ProgressiveImage from '@theme/ProgressiveImage';
 
 
 Whenever the page sends a request for a network resource the following sequence of events are emitted by [Page]:

diff --git a/dotnet/docs/api/class-response.mdx b/dotnet/docs/api/class-response.mdx
@@ -5,7 +5,6 @@ title: "Response"
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import HTMLCard from '@site/src/components/HTMLCard';
-import ProgressiveImage from '@theme/ProgressiveImage';
 
 
 [Response] class represents responses which are received by page.

diff --git a/dotnet/docs/api/class-route.mdx b/dotnet/docs/api/class-route.mdx
@@ -5,7 +5,6 @@ title: "Route"
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import HTMLCard from '@site/src/components/HTMLCard';
-import ProgressiveImage from '@theme/ProgressiveImage';
 
 
 Whenever a network route is set up with [Page.RouteAsync()](/api/class-page.mdx#page-route) or [BrowserContext.RouteAsync()](/api/class-browsercontext.mdx#browser-context-route), the `Route` object allows to handle the route.

diff --git a/dotnet/docs/api/class-selectors.mdx b/dotnet/docs/api/class-selectors.mdx
@@ -5,7 +5,6 @@ title: "Selectors"
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import HTMLCard from '@site/src/components/HTMLCard';
-import ProgressiveImage from '@theme/ProgressiveImage';
 
 
 Selectors can be used to install custom selector engines. See [extensibility](../extensibility.mdx) for more information.

diff --git a/dotnet/docs/api/class-timeouterror.mdx b/dotnet/docs/api/class-timeouterror.mdx
@@ -5,7 +5,6 @@ title: "TimeoutError"
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import HTMLCard from '@site/src/components/HTMLCard';
-import ProgressiveImage from '@theme/ProgressiveImage';
 
 * extends: [Error]
 

diff --git a/dotnet/docs/api/class-touchscreen.mdx b/dotnet/docs/api/class-touchscreen.mdx
@@ -5,7 +5,6 @@ title: "Touchscreen"
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import HTMLCard from '@site/src/components/HTMLCard';
-import ProgressiveImage from '@theme/ProgressiveImage';
 
 
 The Touchscreen class operates in main-frame CSS pixels relative to the top-left corner of the viewport. Methods on the touchscreen can only be used in browser contexts that have been initialized with `hasTouch` set to true.

diff --git a/dotnet/docs/api/class-tracing.mdx b/dotnet/docs/api/class-tracing.mdx
@@ -5,7 +5,6 @@ title: "Tracing"
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import HTMLCard from '@site/src/components/HTMLCard';
-import ProgressiveImage from '@theme/ProgressiveImage';
 
 
 API for collecting and saving Playwright traces. Playwright traces can be opened in [Trace Viewer](../trace-viewer.mdx) after Playwright script runs.

diff --git a/dotnet/docs/api/class-video.mdx b/dotnet/docs/api/class-video.mdx
@@ -5,7 +5,6 @@ title: "Video"
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import HTMLCard from '@site/src/components/HTMLCard';
-import ProgressiveImage from '@theme/ProgressiveImage';
 
 
 When browser context is created with the `recordVideo` option, each page has a video object associated with it.

diff --git a/dotnet/docs/api/class-weberror.mdx b/dotnet/docs/api/class-weberror.mdx
@@ -5,7 +5,6 @@ title: "WebError"
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import HTMLCard from '@site/src/components/HTMLCard';
-import ProgressiveImage from '@theme/ProgressiveImage';
 
 
 [WebError] class represents an unhandled exception thrown in the page. It is dispatched via the [BrowserContext.WebError](/api/class-browsercontext.mdx#browser-context-event-web-error) event.

diff --git a/dotnet/docs/api/class-websocket.mdx b/dotnet/docs/api/class-websocket.mdx
@@ -5,7 +5,6 @@ title: "WebSocket"
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import HTMLCard from '@site/src/components/HTMLCard';
-import ProgressiveImage from '@theme/ProgressiveImage';
 
 
 The [WebSocket] class represents WebSocket connections within a page. It provides the ability to inspect and manipulate the data being transmitted and received.

diff --git a/dotnet/docs/api/class-websocketframe.mdx b/dotnet/docs/api/class-websocketframe.mdx
@@ -5,7 +5,6 @@ title: "WebSocketFrame"
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import HTMLCard from '@site/src/components/HTMLCard';
-import ProgressiveImage from '@theme/ProgressiveImage';
 
 
 The [WebSocketFrame] class represents frames sent over [WebSocket] connections in the page. Frame payload is returned by either [WebSocketFrame.Text](/api/class-websocketframe.mdx#web-socket-frame-text) or [WebSocketFrame.Binary](/api/class-websocketframe.mdx#web-socket-frame-binary) method depending on the its type.

diff --git a/dotnet/docs/api/class-websocketroute.mdx b/dotnet/docs/api/class-websocketroute.mdx
@@ -5,7 +5,6 @@ title: "WebSocketRoute"
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import HTMLCard from '@site/src/components/HTMLCard';
-import ProgressiveImage from '@theme/ProgressiveImage';
 
 
 Whenever a [`WebSocket`](https://developer.mozilla.org/en-US/docs/Web/API/WebSocket) route is set up with [Page.RouteWebSocketAsync()](/api/class-page.mdx#page-route-web-socket) or [BrowserContext.RouteWebSocketAsync()](/api/class-browsercontext.mdx#browser-context-route-web-socket), the `WebSocketRoute` object allows to handle the WebSocket, like an actual server would do.

diff --git a/dotnet/docs/api/class-worker.mdx b/dotnet/docs/api/class-worker.mdx
@@ -5,7 +5,6 @@ title: "Worker"
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import HTMLCard from '@site/src/components/HTMLCard';
-import ProgressiveImage from '@theme/ProgressiveImage';
 
 
 The Worker class represents a [WebWorker](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API). `worker` event is emitted on the page object to signal a worker creation. `close` event is emitted on the worker object when the worker is gone.

diff --git a/dotnet/docs/aria-snapshots.mdx b/dotnet/docs/aria-snapshots.mdx
@@ -5,7 +5,6 @@ title: "Snapshot testing"
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import HTMLCard from '@site/src/components/HTMLCard';
-import ProgressiveImage from '@theme/ProgressiveImage';
 
 import LiteYouTube from '@site/src/components/LiteYouTube';
 

diff --git a/dotnet/docs/auth.mdx b/dotnet/docs/auth.mdx
@@ -5,7 +5,6 @@ title: "Authentication"
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import HTMLCard from '@site/src/components/HTMLCard';
-import ProgressiveImage from '@theme/ProgressiveImage';
 
 ## Introduction
 

diff --git a/dotnet/docs/browser-contexts.mdx b/dotnet/docs/browser-contexts.mdx
@@ -5,7 +5,6 @@ title: "Isolation"
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import HTMLCard from '@site/src/components/HTMLCard';
-import ProgressiveImage from '@theme/ProgressiveImage';
 
 ## Introduction
 

diff --git a/dotnet/docs/browsers.mdx b/dotnet/docs/browsers.mdx
@@ -5,7 +5,6 @@ title: "Browsers"
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import HTMLCard from '@site/src/components/HTMLCard';
-import ProgressiveImage from '@theme/ProgressiveImage';
 
 ## Introduction
 

diff --git a/dotnet/docs/ci-intro.mdx b/dotnet/docs/ci-intro.mdx
@@ -5,7 +5,6 @@ title: "Setting up CI"
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import HTMLCard from '@site/src/components/HTMLCard';
-import ProgressiveImage from '@theme/ProgressiveImage';
 
 ## Introduction
 
@@ -84,7 +83,7 @@ Clicking on the workflow run shows you all the actions that GitHub performed and
 You can upload Traces which get created on your CI like GitHub Actions as artifacts. This requires [starting and stopping the trace](./trace-viewer-intro#recording-a-trace). We recommend only recording traces for failing tests. Once your traces have been uploaded to CI, they can then be downloaded and opened using [trace.playwright.dev](https://trace.playwright.dev), which is a statically hosted variant of the Trace Viewer. You can upload trace files using drag and drop.
 
 ###### 
-<ProgressiveImage image={require("../images/getting-started/trace-viewer-failed-test.png")} alt="playwright trace viewer" />
+![playwright trace viewer](../images/getting-started/trace-viewer-failed-test.png)
 
 ## Properly handling Secrets