playwright-ruby-client 1.41.1 → 1.42.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: e2397db1ea0d9671da0a957aa29d77650584430297826843c9648c49f734d4b4
-  data.tar.gz: e42e6b9b65def3ea385f85b68737d745baa4f4572c407dfdb1b913a1cb7a7f19
+  metadata.gz: 79e99154b04a3b18273674554754ce1b06e49ae03f334b7e780f89d3b2b8c50c
+  data.tar.gz: e0939e8cde7fd6e57ec24896bf26cf0c19a371a500be3f79fa5f284ca7b047b8
 SHA512:
-  metadata.gz: df29b9608775156c8d445377b26346e354c1c2f917df0b36958f65ed353a1fb98aae5db4b5090d2af2f3fe9f2d0087cc39da4c85639f88cad669a21d0d61986d
-  data.tar.gz: 59237bdaca06fcefd34e9d4809d3a06257fd3353acef68a7132cc6c10761f2c659938023e0e87c442a380e79354df21eb1f368c6a52542da7f80dc6169d6130b
+  metadata.gz: 3b9a52e358b44a45294c244e88f1a7646011db15cf02d14f717b69bbaca4a81df90607a3425079a00c63bc185c8a1e4d5859244da007e67a84d9d399a40a5211
+  data.tar.gz: 1f3a94d32ce82afdd196b2cd928f590bd0278f1ea0eb1cf2cc8ae22a31fbaa5a5ab4414b6dbb0916fd0f42cc6c5609d73da48bcb960b4299215516cbe9b1ac99

data/documentation/docs/api/browser_context.md

@@ -311,16 +311,14 @@ page.goto("https://example.com")
 
 It is possible to examine the request to decide the route action. For example, mocking all requests that contain some post data, and leaving all other requests as is:
 
-```ruby
-def handle_route(route, request)
-  if request.post_data["my-string"]
-    mocked_data = request.post_data.merge({ "my-string" => 'mocked-data'})
-    route.fulfill(postData: mocked_data)
-  else
-    route.continue
-  end
-end
-context.route("/api/**", method(:handle_route))
+```python sync title=example_c78483d1434363f907c28aecef3a1c6d83c0136d98bb07c2bd326cd19e006aa9.py
+def handle_route(route: Route):
+  if ("my-string" in route.request.post_data):
+    route.fulfill(body="mocked-data")
+  else:
+    route.continue_()
+context.route("/api/**", handle_route)
+
 ```
 
 Page routes (set up with [Page#route](./page#route)) take precedence over browser context routes when request matches both

data/documentation/docs/api/element_handle.md

@@ -423,7 +423,7 @@ Holding down `Shift` will type the text that corresponds to the `key` in the upp
 If `key` is a single character, it is case-sensitive, so the values `a` and `A` will generate different
 respective texts.
 
-Shortcuts such as `key: "Control+o"` or `key: "Control+Shift+T"` are supported as well. When specified with the
+Shortcuts such as `key: "Control+o"`, `key: "Control++` or `key: "Control+Shift+T"` are supported as well. When specified with the
 modifier, modifier is pressed and being held while the subsequent key is being pressed.
 
 ## query_selector

data/documentation/docs/api/experimental/android.md

@@ -22,12 +22,6 @@ Playwright has **experimental** support for Android automation. This includes Ch
 
 An example of the Android automation script would be:
 
-Note that since you don't need Playwright to install web browsers when testing Android, you can omit browser download via setting the following environment variable when installing Playwright:
-
-```bash js
-PLAYWRIGHT_SKIP_BROWSER_DOWNLOAD=1 npm i -D playwright
-```
-
 ## devices
 
 ```

data/documentation/docs/api/frame.md

@@ -857,7 +857,7 @@ Holding down `Shift` will type the text that corresponds to the `key` in the upp
 If `key` is a single character, it is case-sensitive, so the values `a` and `A` will generate different
 respective texts.
 
-Shortcuts such as `key: "Control+o"` or `key: "Control+Shift+T"` are supported as well. When specified with the
+Shortcuts such as `key: "Control+o"`, `key: "Control++` or `key: "Control+Shift+T"` are supported as well. When specified with the
 modifier, modifier is pressed and being held while the subsequent key is being pressed.
 
 ## query_selector

data/documentation/docs/api/keyboard.md

@@ -114,7 +114,7 @@ Holding down `Shift` will type the text that corresponds to the `key` in the upp
 If `key` is a single character, it is case-sensitive, so the values `a` and `A` will generate different
 respective texts.
 
-Shortcuts such as `key: "Control+o"` or `key: "Control+Shift+T"` are supported as well. When specified with the
+Shortcuts such as `key: "Control+o"`, `key: "Control++` or `key: "Control+Shift+T"` are supported as well. When specified with the
 modifier, modifier is pressed and being held while the subsequent key is being pressed.
 
 **Usage**

data/documentation/docs/api/locator.md

@@ -1056,7 +1056,7 @@ Holding down `Shift` will type the text that corresponds to the `key` in the upp
 If `key` is a single character, it is case-sensitive, so the values `a` and `A` will generate different
 respective texts.
 
-Shortcuts such as `key: "Control+o"` or `key: "Control+Shift+T"` are supported as well. When specified with the
+Shortcuts such as `key: "Control+o"`, `key: "Control++` or `key: "Control+Shift+T"` are supported as well. When specified with the
 modifier, modifier is pressed and being held while the subsequent key is being pressed.
 
 ## press_sequentially

data/documentation/docs/api/page.md

@@ -1077,11 +1077,13 @@ def pdf(
       height: nil,
       landscape: nil,
       margin: nil,
+      outline: nil,
       pageRanges: nil,
       path: nil,
       preferCSSPageSize: nil,
       printBackground: nil,
       scale: nil,
+      tagged: nil,
       width: nil)
 ```
 
@@ -1165,7 +1167,7 @@ Holding down `Shift` will type the text that corresponds to the `key` in the upp
 If `key` is a single character, it is case-sensitive, so the values `a` and `A` will generate different
 respective texts.
 
-Shortcuts such as `key: "Control+o"` or `key: "Control+Shift+T"` are supported as well. When specified with the
+Shortcuts such as `key: "Control+o"`, `key: "Control++` or `key: "Control+Shift+T"` are supported as well. When specified with the
 modifier, modifier is pressed and being held while the subsequent key is being pressed.
 
 **Usage**
@@ -1244,16 +1246,14 @@ page.goto("https://example.com")
 
 It is possible to examine the request to decide the route action. For example, mocking all requests that contain some post data, and leaving all other requests as is:
 
-```ruby
-def handle_route(route, request)
-  if request.post_data["my-string"]
-    mocked_data = request.post_data.merge({ "my-string" => 'mocked-data'})
-    route.fulfill(postData: mocked_data)
-  else
-    route.continue
-  end
-end
-page.route("/api/**", method(:handle_route))
+```python sync title=example_0ef62eead1348f28a69716a047f3b75c979d3230569d3720d4e7bdd0a22ef647.py
+def handle_route(route: Route):
+  if ("my-string" in route.request.post_data):
+    route.fulfill(body="mocked-data")
+  else:
+    route.continue_()
+page.route("/api/**", handle_route)
+
 ```
 
 Page routes take precedence over browser context routes (set up with [BrowserContext#route](./browser_context#route)) when request

data/documentation/docs/include/api_coverage.md

@@ -298,6 +298,7 @@
 * press
 * query_selector
 * query_selector_all
+* ~~add_locator_handler~~
 * reload
 * route
 * route_from_har

data/documentation/docusaurus.config.js

@@ -86,6 +86,12 @@ module.exports = {
     prism: {
       additionalLanguages: ['bash', 'ruby'],
     },
+    algolia: {
+      appId: '00PBL1OR8R',
+      apiKey: '38d9bd4fef84d709547a1ca466ee8241',
+      indexName: 'playwright-ruby-client',
+      contextualSearch: false,
+    }
   },
   presets: [
     [

data/documentation/package.json

@@ -14,8 +14,8 @@
     "write-heading-ids": "docusaurus write-heading-ids"
   },
   "dependencies": {
-    "@docusaurus/core": "^3.0.0",
-    "@docusaurus/preset-classic": "^3.0.0",
+    "@docusaurus/core": "^3.1.1",
+    "@docusaurus/preset-classic": "^3.1.1",
     "@mdx-js/react": "^3.0.0",
     "@svgr/webpack": "^8.1.0",
     "clsx": "^2.0.0",