Merge branch 'trunk' into update-nightly-version

Author: diemol

examples/javascript/test/interactions/windows.spec.js

@@ -85,4 +85,34 @@ describe('Interactions - Windows', function () {
     const windowsAfterClose = await driver.getAllWindowHandles();
     assert.strictEqual(windowsAfterClose.length, 2);
   });
+
+  it('Should be able to getWindow Size', async function () {
+    await driver.get('https://www.selenium.dev/selenium/web/');
+
+    // Access each dimension individually
+    const { width, height } = await driver.manage().window().getRect();
+
+    // Or store the dimensions and query them later
+    const rect = await driver.manage().window().getRect();
+    const windowWidth = rect.width;
+    const windowHeight = rect.height;
+
+    assert.ok(windowWidth>0);
+    assert.ok(windowHeight>0);
+  });
+
+  it('Should be able to getWindow position', async function () {
+    await driver.get('https://www.selenium.dev/selenium/web/');
+
+    // Access each dimension individually
+    const { x, y } = await driver.manage().window().getRect();
+
+    // Or store the dimensions and query them later
+    const rect = await driver.manage().window().getRect();
+    const x1 = rect.x;
+    const y1 = rect.y;
+
+    assert.ok(x1>=0);
+    assert.ok(y1>=0);
+  });
 });

website_and_docs/content/documentation/grid/advanced_features/endpoints.en.md

@@ -19,6 +19,17 @@ For every Node, the status includes information regarding Node availability, ses
 cURL GET 'http://localhost:4444/status'
 ```
 
+### Delete session
+
+Deleting the session terminates the WebDriver session, quits the driver and removes it from the active sessions map.
+Any request using the removed session-id or reusing the driver instance will throw an error.
+
+```shell
+cURL --request DELETE 'http://localhost:4444/session/<session-id>'
+```
+
+### Which URL should I use?
+
 In the Standalone mode, the Grid URL is the Standalone server address.
 
 In the Hub-Node mode, the Grid URL is the Hub server address. 

website_and_docs/content/documentation/grid/advanced_features/endpoints.ja.md

@@ -19,6 +19,17 @@ Grid ステータスは Grid の現在の状態を提供します。 登録さ
 cURL GET 'http://localhost:4444/status'
 ```
 
+### セッションの削除
+
+セッションを削除すると、WebDriver セッションが終了し、ドライバがアクティブなセッションマップから削除されます。
+削除されたセッション ID を使用するリクエストや、ドライバのインスタンスを再利用しようとすると、エラーとなります。
+
+```shell
+cURL --request DELETE 'http://localhost:4444/session/<session-id>'
+```
+
+### Which URL should I use?
+
 スタンドアロンモードでは、Grid URL は スタンドアロンサーバーのアドレスになります。
 
 ハブ&ノードモードでは、Grid URL は ハブのアドレスになります。

website_and_docs/content/documentation/grid/advanced_features/endpoints.pt-br.md

@@ -19,6 +19,17 @@ Para cada nó, o status inclui informações sobre a disponibilidade, sessões e
 cURL GET 'http://localhost:4444/status'
 ```
 
+### Deletar sessão
+
+A exclusão da sessão encerra a sessão do WebDriver, fecha o driver e o remove do mapa de sessões ativas.
+Qualquer solicitação usando o id de sessão removido ou reutilizando a instância do driver gerará um erro.
+
+```shell
+cURL --request DELETE 'http://localhost:4444/session/<session-id>'
+```
+
+### Which URL should I use?
+
 No modo Standalone, o URL da Grid é o endereço do servidor Standalone.
 
 No modo Hub-Node, a URL da Grid é o endereço do servidor Hub.

website_and_docs/content/documentation/grid/advanced_features/endpoints.zh-cn.md

@@ -21,6 +21,16 @@ Grid状态提供Grid的当前状态.
 cURL GET 'http://localhost:4444/status'
 ```
 
+### 检查会话所有者
+
+要检查会话是否属于某一节点, 请使用下面列出的cURL命令. 
+
+```shell
+cURL --request DELETE 'http://localhost:4444/session/<session-id>'
+```
+
+### Which URL should I use?
+
 在独立模式下, Grid URL是独立服务器的地址.
 
 在集线器节点模式下, Grid URL是集线器服务器的地址.

website_and_docs/content/documentation/grid/configuration/cli_options.en.md

@@ -237,6 +237,7 @@ pull request updating this page.
 | `--service-host` | string | `localhost` | Host name where the service that supports WebDriver commands is running |
 | `--service-port` | int | `4723` | Port where the service that supports WebDriver commands is running |
 | `--service-status-endpoint` | string | `/status` | Optional, endpoint to query the WebDriver service status, an HTTP 200 response is expected |
+| `--service-protocol-version` | string | `HTTP/1.1` | Optional, enforce a specific protocol version in HttpClient when communicating with the endpoint service status |
 | `--service-configuration` | string[] | `max-sessions=2 stereotype='{"browserName": "safari", "platformName": "iOS", "appium:platformVersion": "14.5"}}'` | Configuration for the service where calls will be relayed to. It is recommended to provide this type of configuration through a toml config file to improve readability. |
 
 ### Router

website_and_docs/content/documentation/grid/configuration/cli_options.ja.md

@@ -236,6 +236,7 @@ Grid の設定には、さまざまなセクションが用意されています
 | `--service-host`            | string   | `localhost`                                                                                                       | WebDriver コマンドをサポートしてるサービスが稼働しているホスト名。                                          |
 | `--service-port`            | int      | `4723`                                                                                                            | WebDriver コマンドをサポートしてるサービスが稼働しているポート番号。                                        |
 | `--service-status-endpoint` | string   | `/status`                                                                                                         | WebDriver サービスの状態を問い合わせるエンドポイント、オプショナルです。HTTP 200 レスポンスが期待されます。 |
+| `--service-protocol-version` | string | `HTTP/1.1` | Optional, enforce a specific protocol version in HttpClient when communicating with the endpoint service status |
 | `--service-configuration`   | string[] | `max-sessions=2 stereotype='{"browserName": "safari", "platformName": "iOS", "appium:platformVersion": "14.5"}}'` | 呼び出しの中継先となるサービスの設定。可読性向上のため、TOML ファイルで設定することを推奨します。           |
 
 ### Router

website_and_docs/content/documentation/grid/configuration/cli_options.pt-br.md

@@ -240,6 +240,7 @@ e esteja à vontade para nos enviar um pull request com alterações a esta pág
 | `--service-host` | string | `localhost` | Host name where the service that supports WebDriver commands is running |
 | `--service-port` | int | `4723` | Port where the service that supports WebDriver commands is running |
 | `--service-status-endpoint` | string | `/status` | Optional, endpoint to query the WebDriver service status, an HTTP 200 response is expected |
+| `--service-protocol-version` | string | `HTTP/1.1` | Optional, enforce a specific protocol version in HttpClient when communicating with the endpoint service status |
 | `--service-configuration` | string[] | `max-sessions=2 stereotype='{"browserName": "safari", "platformName": "iOS", "appium:platformVersion": "14.5"}}'` | Configuration for the service where calls will be relayed to. It is recommended to provide this type of configuration through a toml config file to improve readability. |
 
 ### Router

website_and_docs/content/documentation/grid/configuration/cli_options.zh-cn.md

@@ -246,6 +246,7 @@ pull request updating this page.
 | `--service-host` | string | `localhost` | Host name where the service that supports WebDriver commands is running |
 | `--service-port` | int | `4723` | Port where the service that supports WebDriver commands is running |
 | `--service-status-endpoint` | string | `/status` | Optional, endpoint to query the WebDriver service status, an HTTP 200 response is expected |
+| `--service-protocol-version` | string | `HTTP/1.1` | Optional, enforce a specific protocol version in HttpClient when communicating with the endpoint service status |
 | `--service-configuration` | string[] | `max-sessions=2 stereotype='{"browserName": "safari", "platformName": "iOS", "appium:platformVersion": "14.5"}}'` | Configuration for the service where calls will be relayed to. It is recommended to provide this type of configuration through a toml config file to improve readability. |
 
 ### Router

website_and_docs/content/documentation/grid/configuration/toml_options.en.md

@@ -134,6 +134,8 @@ detect-drivers = false
 # Default Appium/Cloud server endpoint
 url = "http://localhost:4723/wd/hub"
 status-endpoint = "/status"
+# Optional, enforce a specific protocol version in HttpClient when communicating with the endpoint service status (e.g. HTTP/1.1, HTTP/2)
+protocol-version = "HTTP/1.1"
 # Stereotypes supported by the service. The initial number is "max-sessions", and will allocate 
 # that many test slots to that particular configuration
 configs = [

website_and_docs/content/documentation/grid/configuration/toml_options.ja.md

@@ -131,6 +131,8 @@ detect-drivers = false
 # Default Appium/Cloud server endpoint
 url = "http://localhost:4723/wd/hub"
 status-endpoint = "/status"
+# Optional, enforce a specific protocol version in HttpClient when communicating with the endpoint service status (e.g. HTTP/1.1, HTTP/2)
+protocol-version = "HTTP/1.1"
 # Stereotypes supported by the service. The initial number is "max-sessions", and will allocate
 # that many test slots to that particular configuration
 configs = [

website_and_docs/content/documentation/grid/configuration/toml_options.pt-br.md

@@ -143,6 +143,8 @@ detect-drivers = false
 # Default Appium/Cloud server endpoint
 url = "http://localhost:4723/wd/hub"
 status-endpoint = "/status"
+# Optional, enforce a specific protocol version in HttpClient when communicating with the endpoint service status (e.g. HTTP/1.1, HTTP/2)
+protocol-version = "HTTP/1.1"
 # Stereotypes supported by the service. The initial number is "max-sessions", and will allocate 
 # that many test slots to that particular configuration
 configs = [

website_and_docs/content/documentation/grid/configuration/toml_options.zh-cn.md

@@ -149,6 +149,8 @@ detect-drivers = false
 # Default Appium/Cloud server endpoint
 url = "http://localhost:4723/wd/hub"
 status-endpoint = "/status"
+# Optional, enforce a specific protocol version in HttpClient when communicating with the endpoint service status (e.g. HTTP/1.1, HTTP/2)
+protocol-version = "HTTP/1.1"
 # Stereotypes supported by the service. The initial number is "max-sessions", and will allocate 
 # that many test slots to that particular configuration
 configs = [

website_and_docs/content/documentation/webdriver/interactions/windows.en.md

@@ -515,15 +515,13 @@ size = driver.manage.window.size
 width1 = size.width
 height1 = size.height
   {{< /tab >}}
-  {{< tab header="JavaScript" >}}
-// Access each dimension individually
-const { width, height } = await driver.manage().window().getRect();
+{{< tab header="JavaScript" text=true >}}
+Access each dimension individually
+{{< gh-codeblock path="examples/javascript/test/interactions/windows.spec.js#L93" >}}
 
-// Or store the dimensions and query them later
-const rect = await driver.manage().window().getRect();
-const width1 = rect.width;
-const height1 = rect.height;
-  {{< /tab >}}
+(or) store the dimensions and query them later
+{{< gh-codeblock path="examples/javascript/test/interactions/windows.spec.js#L96-L98" >}}
+{{< /tab >}}
   {{< tab header="Kotlin" >}}
 //Access each dimension individually
 val width = driver.manage().window().size.width
@@ -595,15 +593,13 @@ rect  = driver.manage.window.rect
 x1 = rect.x
 y1 = rect.y
   {{< /tab >}}
-  {{< tab header="JavaScript" >}}
-// Access each dimension individually
-const { x, y } = await driver.manage().window().getRect();
+{{< tab header="JavaScript" text=true >}}
+Access each dimension individually
+{{< gh-codeblock path="examples/javascript/test/interactions/windows.spec.js#L108" >}}
 
-// Or store the dimensions and query them later
-const rect = await driver.manage().window().getRect();
-const x1 = rect.x;
-const y1 = rect.y;
-  {{< /tab >}}
+(or) store the dimensions and query them later
+{{< gh-codeblock path="examples/javascript/test/interactions/windows.spec.js#L111-L113" >}}
+{{< /tab >}}
   {{< tab header="Kotlin" >}}
 // Access each dimension individually
 val x = driver.manage().window().position.x

website_and_docs/content/documentation/webdriver/interactions/windows.ja.md

@@ -487,15 +487,13 @@ size = driver.manage.window.size
 width1 = size.width
 height1 = size.height
   {{< /tab >}}
-  {{< tab header="JavaScript" >}}
-// Access each dimension individually
-const { width, height } = await driver.manage().window().getRect();
+{{< tab header="JavaScript" text=true >}}
+Access each dimension individually
+{{< gh-codeblock path="examples/javascript/test/interactions/windows.spec.js#L93" >}}
 
-// Or store the dimensions and query them later
-const rect = await driver.manage().window().getRect();
-const width1 = rect.width;
-const height1 = rect.height;
-  {{< /tab >}}
+(or) store the dimensions and query them later
+{{< gh-codeblock path="examples/javascript/test/interactions/windows.spec.js#L96-L98" >}}
+{{< /tab >}}
   {{< tab header="Kotlin" >}}
 //Access each dimension individually
 val width = driver.manage().window().size.width
@@ -566,15 +564,13 @@ rect  = driver.manage.window.rect
 x1 = rect.x
 y1 = rect.y
   {{< /tab >}}
-  {{< tab header="JavaScript" >}}
-// Access each dimension individually
-const { x, y } = await driver.manage().window().getRect();
+{{< tab header="JavaScript" text=true >}}
+Access each dimension individually
+{{< gh-codeblock path="examples/javascript/test/interactions/windows.spec.js#L108" >}}
 
-// Or store the dimensions and query them later
-const rect = await driver.manage().window().getRect();
-const x1 = rect.x;
-const y1 = rect.y;
-  {{< /tab >}}
+(or) store the dimensions and query them later
+{{< gh-codeblock path="examples/javascript/test/interactions/windows.spec.js#L111-L113" >}}
+{{< /tab >}}
   {{< tab header="Kotlin" >}}
 // Access each dimension individually
 val x = driver.manage().window().position.x

website_and_docs/content/documentation/webdriver/interactions/windows.pt-br.md

@@ -503,15 +503,13 @@ size = driver.manage.window.size
 width1 = size.width
 height1 = size.height
   {{< /tab >}}
-  {{< tab header="JavaScript" >}}
-// Access each dimension individually
-const { width, height } = await driver.manage().window().getRect();
+{{< tab header="JavaScript" text=true >}}
+Access each dimension individually
+{{< gh-codeblock path="examples/javascript/test/interactions/windows.spec.js#L93" >}}
 
-// Or store the dimensions and query them later
-const rect = await driver.manage().window().getRect();
-const width1 = rect.width;
-const height1 = rect.height;
-  {{< /tab >}}
+(or) store the dimensions and query them later
+{{< gh-codeblock path="examples/javascript/test/interactions/windows.spec.js#L96-L98" >}}
+{{< /tab >}}
   {{< tab header="Kotlin" >}}
 //Access each dimension individually
 val width = driver.manage().window().size.width
@@ -581,15 +579,13 @@ rect  = driver.manage.window.rect
 x1 = rect.x
 y1 = rect.y
   {{< /tab >}}
-  {{< tab header="JavaScript" >}}
-// Access each dimension individually
-const { x, y } = await driver.manage().window().getRect();
+{{< tab header="JavaScript" text=true >}}
+Access each dimension individually
+{{< gh-codeblock path="examples/javascript/test/interactions/windows.spec.js#L108" >}}
 
-// Or store the dimensions and query them later
-const rect = await driver.manage().window().getRect();
-const x1 = rect.x;
-const y1 = rect.y;
-  {{< /tab >}}
+(or) store the dimensions and query them later
+{{< gh-codeblock path="examples/javascript/test/interactions/windows.spec.js#L111-L113" >}}
+{{< /tab >}}
   {{< tab header="Kotlin" >}}
 // Access each dimension individually
 val x = driver.manage().window().position.x

website_and_docs/content/documentation/webdriver/interactions/windows.zh-cn.md

@@ -468,14 +468,12 @@ size = driver.manage.window.size
 width1 = size.width
 height1 = size.height
 {{< /tab >}}
-{{< tab header="JavaScript" >}}
-// 分别获取每个尺寸
-const {width, height} = await driver.manage().window().getRect();
+{{< tab header="JavaScript" text=true >}}
+分别获取每个尺寸
+{{< gh-codeblock path="examples/javascript/test/interactions/windows.spec.js#L93" >}}
 
-// 或者存储尺寸并在以后查询它们
-const rect = await driver.manage().window().getRect();
-const width1 = rect.width;
-const height1 = rect.height;
+或者存储尺寸并在以后查询它们
+{{< gh-codeblock path="examples/javascript/test/interactions/windows.spec.js#L96-L98" >}}
 {{< /tab >}}
 {{< tab header="Kotlin" >}}
 // 分别获取每个尺寸
@@ -546,14 +544,12 @@ rect  = driver.manage.window.rect
 x1 = rect.x
 y1 = rect.y
 {{< /tab >}}
-{{< tab header="JavaScript" >}}
-// 分别获取每个尺寸
-const {x, y} = await driver.manage().window().getRect();
+{{< tab header="JavaScript" text=true >}}
+分别获取每个尺寸
+{{< gh-codeblock path="examples/javascript/test/interactions/windows.spec.js#L108" >}}
 
-// 或者存储尺寸并在以后查询它们
-const rect = await driver.manage().window().getRect();
-const x1 = rect.x;
-const y1 = rect.y;
+或者存储尺寸并在以后查询它们
+{{< gh-codeblock path="examples/javascript/test/interactions/windows.spec.js#L111-L113" >}}
 {{< /tab >}}
 {{< tab header="Kotlin" >}}
 // 分别获取每个尺寸

website_and_docs/content/documentation/webdriver/waits.en.md

@@ -92,7 +92,7 @@ _Explicit waits_ are loops added to the code that poll the application
 for a specific condition to evaluate as true before it exits the loop and
 continues to the next command in the code. If the condition is not met before a designated timeout value, 
 the code will give a timeout error. Since there are many ways for the application not to be in the desired state,
-so explicit waits are a great choice to specify the exact condition to wait for
+explicit waits are a great choice to specify the exact condition to wait for
 in each place it is needed. 
 Another nice feature is that, by default, the Selenium Wait class automatically waits for the designated element to exist.
 

website_and_docs/content/documentation/webdriver/waits.ja.md

@@ -92,7 +92,7 @@ _Explicit waits_ are loops added to the code that poll the application
 for a specific condition to evaluate as true before it exits the loop and
 continues to the next command in the code. If the condition is not met before a designated timeout value,
 the code will give a timeout error. Since there are many ways for the application not to be in the desired state,
-so explicit waits are a great choice to specify the exact condition to wait for
+explicit waits are a great choice to specify the exact condition to wait for
 in each place it is needed.
 Another nice feature is that, by default, the Selenium Wait class automatically waits for the designated element to exist.
 

website_and_docs/content/documentation/webdriver/waits.pt-br.md

@@ -92,7 +92,7 @@ _Explicit waits_ are loops added to the code that poll the application
 for a specific condition to evaluate as true before it exits the loop and
 continues to the next command in the code. If the condition is not met before a designated timeout value,
 the code will give a timeout error. Since there are many ways for the application not to be in the desired state,
-so explicit waits are a great choice to specify the exact condition to wait for
+explicit waits are a great choice to specify the exact condition to wait for
 in each place it is needed.
 Another nice feature is that, by default, the Selenium Wait class automatically waits for the designated element to exist.
 

website_and_docs/content/documentation/webdriver/waits.zh-cn.md

@@ -92,7 +92,7 @@ _Explicit waits_ are loops added to the code that poll the application
 for a specific condition to evaluate as true before it exits the loop and
 continues to the next command in the code. If the condition is not met before a designated timeout value,
 the code will give a timeout error. Since there are many ways for the application not to be in the desired state,
-so explicit waits are a great choice to specify the exact condition to wait for
+explicit waits are a great choice to specify the exact condition to wait for
 in each place it is needed.
 Another nice feature is that, by default, the Selenium Wait class automatically waits for the designated element to exist.