docs(trace-viewer): viewing remote traces on trace.playwright.dev (#12363)

.github/workflows/test_test_runner.yml

@@ -6,8 +6,6 @@ on:
       - release-*
     paths:
       - ".github/workflows/test_test_runner.yml"
-      - "!browser_patches/**"
-      - "!docs/**"
       - "tests/playwright-test/**/*"
       - "packages/playwright-test/**/*"
       - "package.json"
@@ -17,8 +15,6 @@ on:
       - release-*
     paths:
       - ".github/workflows/test_test_runner.yml"
-      - "!browser_patches/**"
-      - "!docs/**"
       - "tests/playwright-test/**/*"
       - "packages/playwright-test/**/*"
       - "package.json"

docs/src/trace-viewer.md

@@ -222,3 +222,19 @@ playwright show-trace https://example.com/trace.zip
 ```bash csharp
 pwsh bin\Debug\netX\playwright.ps1 show-trace https://example.com/trace.zip
 ```
+
+## Using [trace.playwright.dev](https://trace.playwright.dev)
+
+[trace.playwright.dev](https://trace.playwright.dev) is a statically hosted variant of the Trace Viewer. 
+
+### Viewing local traces
+
+When navigating to [trace.playwright.dev](https://trace.playwright.dev), you can upload trace files using drag and drop.
+
+### Remote traces
+
+You can also pass the URL of your uploaded trace (e.g. inside your CI) from some accessible storage as a parameter. CORS (Cross-Origin Resource Sharing) rules might apply.
+
+```txt
+https://trace.playwright.dev/?trace=https://demo.playwright.dev/reports/todomvc/data/cb0fa77ebd9487a5c899f3ae65a7ffdbac681182.zip
+```