feat(roll): roll to ToT Playwright (08-10-24)

dotnet/docs/api/class-clock.mdx

@@ -145,6 +145,8 @@ await page.Clock.RunForAsync("30:00");
 
 Makes `Date.now` and `new Date()` return fixed fake time at all times, keeps all the timers running.
 
+Use this method for simple scenarios where you only need to test with a predefined time. For more advanced scenarios, use [Clock.InstallAsync()](/api/class-clock.mdx#clock-install) instead. Read docs on [clock emulation](../clock.mdx) to learn more.
+
 **Usage**
 
 ```csharp
@@ -167,7 +169,7 @@ await page.Clock.SetFixedTimeAsync("2020-02-02");
 
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.45</font><x-search>clock.SetSystemTimeAsync</x-search>
 
-Sets current system time but does not trigger any timers.
+Sets system time, but does not trigger any timers. Use this to test how the web page reacts to a time shift, for example switching from summer to winter time, or changing time zones.
 
 **Usage**
 

dotnet/docs/api/class-route.mdx

@@ -89,7 +89,7 @@ await page.RouteAsync("**/*", async route =>
 
 **Details**
 
-Note that any overrides such as [Url](/api/class-route.mdx#route-continue-option-url) or [Headers](/api/class-route.mdx#route-continue-option-headers) only apply to the request being routed. If this request results in a redirect, overrides will not be applied to the new redirected request. If you want to propagate a header through redirects, use the combination of [Route.FetchAsync()](/api/class-route.mdx#route-fetch) and [Route.FulfillAsync()](/api/class-route.mdx#route-fulfill) instead.
+The [Headers](/api/class-route.mdx#route-continue-option-headers) option applies to both the routed request and any redirects it initiates. However, [Url](/api/class-route.mdx#route-continue-option-url), [Method](/api/class-route.mdx#route-continue-option-method), and [PostData](/api/class-route.mdx#route-continue-option-post-data) only apply to the original request and are not carried over to redirected requests.
 
 [Route.ContinueAsync()](/api/class-route.mdx#route-continue) will immediately send the request to the network, other matching handlers won't be invoked. Use [Route.FallbackAsync()](/api/class-route.mdx#route-fallback) If you want next matching handler in the chain to be invoked.
 

java/docs/api/class-clock.mdx

@@ -147,6 +147,8 @@ page.clock().runFor("30:00");
 
 Makes `Date.now` and `new Date()` return fixed fake time at all times, keeps all the timers running.
 
+Use this method for simple scenarios where you only need to test with a predefined time. For more advanced scenarios, use [Clock.install()](/api/class-clock.mdx#clock-install) instead. Read docs on [clock emulation](../clock.mdx) to learn more.
+
 **Usage**
 
 ```java
@@ -169,7 +171,7 @@ page.clock().setFixedTime("2020-02-02");
 
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.45</font><x-search>clock.setSystemTime</x-search>
 
-Sets current system time but does not trigger any timers.
+Sets system time, but does not trigger any timers. Use this to test how the web page reacts to a time shift, for example switching from summer to winter time, or changing time zones.
 
 **Usage**
 

java/docs/api/class-route.mdx

@@ -301,7 +301,7 @@ page.route("**/*", route -> {
 
 **Details**
 
-Note that any overrides such as [setUrl](/api/class-route.mdx#route-continue-option-url) or [setHeaders](/api/class-route.mdx#route-continue-option-headers) only apply to the request being routed. If this request results in a redirect, overrides will not be applied to the new redirected request. If you want to propagate a header through redirects, use the combination of [Route.fetch()](/api/class-route.mdx#route-fetch) and [Route.fulfill()](/api/class-route.mdx#route-fulfill) instead.
+The [setHeaders](/api/class-route.mdx#route-continue-option-headers) option applies to both the routed request and any redirects it initiates. However, [setUrl](/api/class-route.mdx#route-continue-option-url), [setMethod](/api/class-route.mdx#route-continue-option-method), and [setPostData](/api/class-route.mdx#route-continue-option-post-data) only apply to the original request and are not carried over to redirected requests.
 
 [Route.resume()](/api/class-route.mdx#route-continue) will immediately send the request to the network, other matching handlers won't be invoked. Use [Route.fallback()](/api/class-route.mdx#route-fallback) If you want next matching handler in the chain to be invoked.
 

nodejs/docs/api/class-clock.mdx

@@ -146,6 +146,8 @@ await page.clock.runFor('30:00');
 
 Makes `Date.now` and `new Date()` return fixed fake time at all times, keeps all the timers running.
 
+Use this method for simple scenarios where you only need to test with a predefined time. For more advanced scenarios, use [clock.install()](/api/class-clock.mdx#clock-install) instead. Read docs on [clock emulation](../clock.mdx) to learn more.
+
 **Usage**
 
 ```js
@@ -168,7 +170,7 @@ await page.clock.setFixedTime('2020-02-02');
 
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.45</font><x-search>clock.setSystemTime</x-search>
 
-Sets current system time but does not trigger any timers.
+Sets system time, but does not trigger any timers. Use this to test how the web page reacts to a time shift, for example switching from summer to winter time, or changing time zones.
 
 **Usage**
 

nodejs/docs/api/class-route.mdx

@@ -93,7 +93,7 @@ await page.route('**/*', async (route, request) => {
 
 **Details**
 
-Note that any overrides such as [url](/api/class-route.mdx#route-continue-option-url) or [headers](/api/class-route.mdx#route-continue-option-headers) only apply to the request being routed. If this request results in a redirect, overrides will not be applied to the new redirected request. If you want to propagate a header through redirects, use the combination of [route.fetch()](/api/class-route.mdx#route-fetch) and [route.fulfill()](/api/class-route.mdx#route-fulfill) instead.
+The [headers](/api/class-route.mdx#route-continue-option-headers) option applies to both the routed request and any redirects it initiates. However, [url](/api/class-route.mdx#route-continue-option-url), [method](/api/class-route.mdx#route-continue-option-method), and [postData](/api/class-route.mdx#route-continue-option-post-data) only apply to the original request and are not carried over to redirected requests.
 
 [route.continue()](/api/class-route.mdx#route-continue) will immediately send the request to the network, other matching handlers won't be invoked. Use [route.fallback()](/api/class-route.mdx#route-fallback) If you want next matching handler in the chain to be invoked.
 

python/docs/api/class-clock.mdx

@@ -208,6 +208,8 @@ await page.clock.run_for("30:00")
 
 Makes `Date.now` and `new Date()` return fixed fake time at all times, keeps all the timers running.
 
+Use this method for simple scenarios where you only need to test with a predefined time. For more advanced scenarios, use [clock.install()](/api/class-clock.mdx#clock-install) instead. Read docs on [clock emulation](../clock.mdx) to learn more.
+
 **Usage**
 
 <Tabs
@@ -252,7 +254,7 @@ await page.clock.set_fixed_time("2020-02-02")
 
 <font size="2" style={{position: "relative", top: "-20px"}}>Added in: v1.45</font><x-search>clock.set_system_time</x-search>
 
-Sets current system time but does not trigger any timers.
+Sets system time, but does not trigger any timers. Use this to test how the web page reacts to a time shift, for example switching from summer to winter time, or changing time zones.
 
 **Usage**
 

python/docs/api/class-route.mdx

@@ -122,7 +122,7 @@ await page.route("**/*", handle)
 
 **Details**
 
-Note that any overrides such as [url](/api/class-route.mdx#route-continue-option-url) or [headers](/api/class-route.mdx#route-continue-option-headers) only apply to the request being routed. If this request results in a redirect, overrides will not be applied to the new redirected request. If you want to propagate a header through redirects, use the combination of [route.fetch()](/api/class-route.mdx#route-fetch) and [route.fulfill()](/api/class-route.mdx#route-fulfill) instead.
+The [headers](/api/class-route.mdx#route-continue-option-headers) option applies to both the routed request and any redirects it initiates. However, [url](/api/class-route.mdx#route-continue-option-url), [method](/api/class-route.mdx#route-continue-option-method), and [post_data](/api/class-route.mdx#route-continue-option-post-data) only apply to the original request and are not carried over to redirected requests.
 
 [route.continue_()](/api/class-route.mdx#route-continue) will immediately send the request to the network, other matching handlers won't be invoked. Use [route.fallback()](/api/class-route.mdx#route-fallback) If you want next matching handler in the chain to be invoked.