Merge branch 'trunk' into patch-1

Author: boris779

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

@@ -21,19 +21,19 @@ Grid状态提供Grid的当前状态.
 cURL GET 'http://localhost:4444/status'
 ```
 
-### 检查会话所有者
+### 删除会话
 
-要检查会话是否属于某一节点, 请使用下面列出的cURL命令. 
+删除会话会终止 WebDriver 会话、退出驱动程序并将其从活动会话映射中删除。任何使用删除的会话标识或重新使用驱动程序实例的请求都会出错。
 
 ```shell
 cURL --request DELETE 'http://localhost:4444/session/<session-id>'
 ```
 
-### Which URL should I use?
+### 我应该使用哪一个URL?
 
-在独立模式下, Grid URL是独立服务器的地址.
+在 Standalone 模式下, Grid URL是独立服务器的地址.
 
-在集线器节点模式下, Grid URL是集线器服务器的地址.
+在 Hub-Node 模式下, Grid URL是集线器服务器的地址.
 
 在完全分布式模式下, Grid URL是路由服务器的地址.
 
@@ -43,90 +43,66 @@ cURL --request DELETE 'http://localhost:4444/session/<session-id>'
 
 ### 删除节点
 
-要从Grid中删除节点, 
-请使用下面列出的cURL命令.
-它不会停止在该节点上运行的任何持续中的会话.
-除非显式终止, 否则节点将继续按原样运行.
-分发器不再知晓该节点,
-因此任何匹配的新会话请求
-也不会转发到该节点.
+要从网格中删除节点，请使用下面列出的 cURL 命令。该命令不会停止正在该节点上运行的任何会话。除非显式终止, 否则节点将继续运行。分发器不再知道该节点，因此任何匹配的新会话请求都不会转发到该节点。
 
-在独立模式下, 分发器URL是独立服务器的地址.
+在 Standalone 模式下，分发器 URL 是独立服务器地址。
 
-在集线器节点模式下, 分发器URL是集线器服务器的地址. 
+在 Hub-Node 模式下, 分发器 URL 是 Hub 服务器的地址。
 
 ```shell
 cURL --request DELETE 'http://localhost:4444/se/grid/distributor/node/<node-id>' --header 'X-REGISTRATION-SECRET: <secret> '
 ```
-在完全分布式模式下, URL是分发器的地址.
+在完全分布式模式下, URL是分发器的地址。
 
 ```shell
 cURL --request DELETE 'http://localhost:4444/se/grid/distributor/node/<node-id>' --header 'X-REGISTRATION-SECRET: <secret>'
 ```
-如果在设置Grid时未配置注册密码, 
-则使用
+如果在设置Grid时未配置注册密码, 则使用
 ```shell
 cURL --request DELETE 'http://<Router-URL>/se/grid/distributor/node/<node-id>' --header 'X-REGISTRATION-SECRET;'
 ```
 
-### 放空节点
+### 释放节点
 
-节点放空命令用于优雅地关闭节点.
-放空节点将在所有持续中的会话完成后停止节点.
-但是, 它不接受任何新的会话请求.
+节点释放命令用于优雅地关闭节点。在所有正在进行的会话结束后，会停止该节点。并且，它不会接受任何新的会话请求。
 
-在独立模式下, 分发器URL是独立服务器的地址.
+在 Standalone 模式下，分发器 URL 是独立服务器地址。
 
-在集线器节点模式下, 分发器URL是集线器服务器的地址.
+在 Hub-Node 模式下, 分发器 URL 是 Hub 服务器的地址。
 ```shell
 cURL --request POST 'http://localhost:4444/se/grid/distributor/node/<node-id>/drain' --header 'X-REGISTRATION-SECRET: <secret> '
 ```
-在完全分布式模式下, URL是分发服务器的地址.
+在完全分布式模式下, URL是分发服务器的地址。
 ```shell
 cURL --request POST 'http://localhost:4444/se/grid/distributor/node/<node-id>/drain' --header 'X-REGISTRATION-SECRET: <secret>'
 ```
-如果在设置Grid时未配置注册密码, 
-则使用
+如果在设置Grid时未配置注册密码, 则使用
 ```shell
 cURL --request POST 'http://<Router-URL>/se/grid/distributor/node/<node-id>/drain' --header 'X-REGISTRATION-SECRET;'
 ```
 
 ## 节点
 
-本节中的端点适用于
-集线器节点模式和
-节点独立运行的完全分布式网格模式.
-在一个节点的情况下, 默认节点的URL为 http://localhost:5555 .
-如果有多个节点,
-请使用 [Grid 状态](#grid-状态) 获取所有节点详细信息
-以及定位地址.
+本节中的端点适用于 Hub-Node 模式和节点独立运行的完全分布式网格模式。在一个节点的情况下, 默认节点的URL为 http://localhost:5555 。
+如果有多个节点,请使用 [Grid 状态](#grid-状态) 获取所有节点的详细信息并查找节点地址。
 
 ### 状态 
 
-节点状态本质上是节点的运行状况检查.
-分发器定期ping节点状态，
-并相应地更新Grid模型.
-状态包括相关的可用性, 会话和插槽的信息.
+节点状态本质上是节点的健康检查。分发程序会定期 ping 节点状态，并相应地更新 Grid 模型。状态包括有关可用性、会话和插槽的信息。
 
 ```shell
 cURL --request GET 'http://localhost:5555/status'
 ```
 
-### 放空
+### 释放
 
-分发器将 [放空](#放空节点) 命令传递给
-由node-id标识的相应节点.
-要直接放空节点,
-请使用下面列出的cuRL命令.
-两个端点都有效并产生相同的结果.
-放空会等待持续中的会话完成后
-才停止节点.
+分发器将 [释放](#释放节点) 命令传递给由node-id标识的相应节点。要直接释放节点,请使用下面列出的cuRL命令。
+两个端点都有效并产生相同的结果。释放会等待持续中的会话完成后才停止节点。
 
 ```shell
 cURL --request POST 'http://localhost:5555/se/grid/node/drain' --header 'X-REGISTRATION-SECRET: <secret>'
 ```
-如果在设置Grid时未配置注册密码,
-则使用
+如果在设置Grid时未配置注册密码,则使用
 ```shell
 cURL --request POST 'http://<node-URL>/se/grid/node/drain' --header 'X-REGISTRATION-SECRET;'
 ```
@@ -138,30 +114,23 @@ cURL --request POST 'http://<node-URL>/se/grid/node/drain' --header 'X-REGISTRAT
 ```shell
 cURL --request GET 'http://localhost:5555/se/grid/node/owner/<session-id>' --header 'X-REGISTRATION-SECRET: <secret>'
 ```
-如果在设置Grid时未配置注册密码, 
-则使用
+如果在设置Grid时未配置注册密码, 则使用
 ```shell
 cURL --request GET 'http://<node-URL>/se/grid/node/owner/<session-id>' --header 'X-REGISTRATION-SECRET;'
 ```
 
 如果会话属于该节点, 
 则返回true, 
-否则返回false.
+否则返回false。
 
 ### 删除会话
 
-删除会话将终止WebDriver会话,
-退出驱动程序
-并将其从活动会话集合中删除. 
-任何使用删除的会话id
-或重用驱动程序实例的请求
-都将抛出错误. 
+删除会话会终止 WebDriver 会话、退出驱动程序并将其从活动会话映射中删除。任何使用删除的会话标识或重新使用驱动程序实例的请求都会出错。
 
 ```shell
 cURL --request DELETE 'http://localhost:5555/se/grid/node/session/<session-id>' --header 'X-REGISTRATION-SECRET: <secret>'
 ```
-如果在设置Grid时未配置注册密码, 
-则使用
+如果在设置Grid时未配置注册密码, 则使用
 ```shell
 cURL --request DELETE 'http://<node-URL>/se/grid/node/session/<session-id>' --header 'X-REGISTRATION-SECRET;'
 ```
@@ -170,52 +139,41 @@ cURL --request DELETE 'http://<node-URL>/se/grid/node/session/<session-id>' --he
 
 ### 清除新会话队列
 
-新会话请求队列保存新会话请求.
-要清除队列, 
-请使用下面列出的cURL命令.
-清除队列将拒绝队列中的所有请求.
-对于每个这样的请求, 
-服务器都会向相应的客户端返回一个错误响应.
-清除命令的返回结果是
-已删除请求的总数.
+新会话请求队列保存新会话请求。要清除队列，请使用下面列出的 cURL 命令。清除队列会拒绝队列中的所有请求。对于每个此类请求，服务器都会向相应的客户端返回错误响应。清除命令的结果是被删除请求的总数。
 
-在独立模式下, 队列URL是独立服务器的地址. 
-在集线器节点模式下, 队列URL是集线器服务器的地址. 
+在 Standalone 模式下, 队列URL是独立服务器的地址。
+在 Hub-Node 模式下, 队列URL是集线器服务器的地址。
 
 ```shell
 cURL --request DELETE 'http://localhost:4444/se/grid/newsessionqueue/queue' --header 'X-REGISTRATION-SECRET: <secret>'
 ```
 
 在完全分布式模式下,
-队列URL是新会话队列服务器的地址.
+队列URL是新会话队列服务器的地址。
 ```shell
 cURL --request DELETE 'http://localhost:4444/se/grid/newsessionqueue/queue' --header 'X-REGISTRATION-SECRET: <secret>'
 ```
 
-如果在设置Grid时未配置注册密码, 
-则使用
+如果在设置Grid时未配置注册密码, 则使用
 ```shell
 cURL --request DELETE 'http://<Router-URL>/se/grid/newsessionqueue/queue' --header 'X-REGISTRATION-SECRET;'
 ```
 
 ### 获取新会话队列请求
 
-New Session Request Queue holds the new session requests. 
-To get the current requests in the queue, use the cURL command enlisted below. 
-The response returns the total number of requests in the queue and the request payloads.
-新会话请求队列保存新会话请求.
+新会话请求队列保存新会话请求。
 要获取队列中的当前请求,
-请使用下面列出的cURL命令.
-响应会返回队列中的请求总数以及请求内容.
+请使用下面列出的cURL命令。
+响应会返回队列中的请求总数以及请求内容。
 
-在独立模式下, 队列URL是独立服务器的地址.
-在集线器节点模式下, 队列URL是集线器服务器的地址.
+在 Standalone 模式下, 队列URL是独立服务器的地址。
+在 Hub-Node 模式下, 队列URL是集线器服务器的地址。
 
 ```shell
 cURL --request GET 'http://localhost:4444/se/grid/newsessionqueue/queue'
 ```
 
 在完全分布式模式下,
-队列URL是新会话队列服务器的地址.
+队列URL是新会话队列服务器的地址。
 ```shell
 cURL --request GET 'http://localhost:4444/se/grid/newsessionqueue/queue'

website_and_docs/content/documentation/webdriver/browsers/firefox.en.md

@@ -135,7 +135,16 @@ options.profile = FirefoxProfile()
 driver = FirefoxDriver(options)
   {{< /tab >}}
 {{< /tabpane >}}
-
+**Note**: Whether you create an empty `FirefoxProfile` or point it to the directory of your own profile, Selenium
+will create a temporary directory to store either the data of the new profile or a copy of your existing one. Every
+time you run your program, a different temporary directory will be created. These directories are not cleaned up
+explicitly by Selenium, they should eventually get removed by the operating system. However, if you want to remove
+the copy manually (e.g. if your profile is large in size), the path of the copy is exposed by the `FirefoxProfile`
+object. Check the language specific implementation to see how to retrieve that location.
+
+If you want to use an existing Firefox profile, you can pass in the path to that profile. Please refer to the official
+[Firefox documentation](https://support.mozilla.org/en-US/kb/profiles-where-firefox-stores-user-data#w_how-do-i-find-my-profile)
+for instructions on how to find the directory of your profile.
 
 ## Service
 

website_and_docs/content/documentation/webdriver/browsers/firefox.ja.md

@@ -141,6 +141,16 @@ driver = RemoteWebDriver(options)
 {{< /tabpane >}}
 </div>
 
+**Note**: Whether you create an empty `FirefoxProfile` or point it to the directory of your own profile, Selenium
+will create a temporary directory to store either the data of the new profile or a copy of your existing one. Every
+time you run your program, a different temporary directory will be created. These directories are not cleaned up
+explicitly by Selenium, they should eventually get removed by the operating system. However, if you want to remove
+the copy manually (e.g. if your profile is large in size), the path of the copy is exposed by the `FirefoxProfile`
+object. Check the language specific implementation to see how to retrieve that location.
+
+If you want to use an existing Firefox profile, you can pass in the path to that profile. Please refer to the official
+[Firefox documentation](https://support.mozilla.org/en-US/kb/profiles-where-firefox-stores-user-data#w_how-do-i-find-my-profile)
+for instructions on how to find the directory of your profile.
 
 ## サービス
 

website_and_docs/content/documentation/webdriver/browsers/firefox.pt-br.md

@@ -140,6 +140,16 @@ driver = RemoteWebDriver(options)
 {{< /tabpane >}}
 </div>
 
+**Note**: Whether you create an empty `FirefoxProfile` or point it to the directory of your own profile, Selenium
+will create a temporary directory to store either the data of the new profile or a copy of your existing one. Every
+time you run your program, a different temporary directory will be created. These directories are not cleaned up
+explicitly by Selenium, they should eventually get removed by the operating system. However, if you want to remove
+the copy manually (e.g. if your profile is large in size), the path of the copy is exposed by the `FirefoxProfile`
+object. Check the language specific implementation to see how to retrieve that location.
+
+If you want to use an existing Firefox profile, you can pass in the path to that profile. Please refer to the official
+[Firefox documentation](https://support.mozilla.org/en-US/kb/profiles-where-firefox-stores-user-data#w_how-do-i-find-my-profile)
+for instructions on how to find the directory of your profile.
 
 ## Service
 

website_and_docs/content/documentation/webdriver/browsers/firefox.zh-cn.md

@@ -139,6 +139,16 @@ driver = RemoteWebDriver(options)
 {{< /tabpane >}}
 </div>
 
+**Note**: Whether you create an empty `FirefoxProfile` or point it to the directory of your own profile, Selenium
+will create a temporary directory to store either the data of the new profile or a copy of your existing one. Every
+time you run your program, a different temporary directory will be created. These directories are not cleaned up
+explicitly by Selenium, they should eventually get removed by the operating system. However, if you want to remove
+the copy manually (e.g. if your profile is large in size), the path of the copy is exposed by the `FirefoxProfile`
+object. Check the language specific implementation to see how to retrieve that location.
+
+If you want to use an existing Firefox profile, you can pass in the path to that profile. Please refer to the official
+[Firefox documentation](https://support.mozilla.org/en-US/kb/profiles-where-firefox-stores-user-data#w_how-do-i-find-my-profile)
+for instructions on how to find the directory of your profile.
 
 ## Service
 

website_and_docs/content/sponsor/_index.html

@@ -52,7 +52,8 @@ <h2 class="alert-heading pb-3">General Benefits</h2>
           </li>
           <li>
             Our website is the first place people learn about Selenium. By having a link to your
-            website, you will be seen as a supporter of the Selenium project that our users adore.          </li>
+            website, you will be seen as a supporter of the Selenium project that our users adore.
+          </li>
           <li>
             Contributions are tax-deductible.
           </li>
@@ -64,7 +65,6 @@ <h2 class="alert-heading pb-3">General Benefits</h2>
             Check the <a href="#support-levels">Sponsorship Levels</a> for more benefits.
           </li>
         </ul>
-      </p>
     </div>
   </div>
 </div>
@@ -115,7 +115,7 @@ <h2 class="alert-heading pb-3" id="support-levels">Sponsorship Levels</h2>
           needs to be actively contributing to the project.
         </li>
         <li>
-          Currently limited to 2 companies but reviewed yearly.
+          Currently limited to 3 companies but reviewed yearly.
         </li>
         <li>Special mention at Selenium events</li>
         <li>

website_and_docs/data/sponsors.yml

@@ -9,6 +9,10 @@ development:
     - logo: "/images/sponsors/saucelabs.png"
       url: "https://saucelabs.com/resources/topic-hub/selenium?utm_source=selenium&utm_medium=website&utm_campaign=selenium-sponsorship-fy25"
       name: "Sauce Labs"
+    # Sponsorship renewed October 16, 2024. Renewed again on April 8, 2025, under the "Development" level
+    - logo: "/images/sponsors/lambda-test.png"
+      url: "https://www.lambdatest.com/selenium-automation?utm_source=selenium&utm_medium=open-source-sponsor&utm_campaign=nov_14&utm_term=sk&utm_content=web"
+      name: "LambdaTest"
 
 selenium:
   # Set to false if no items are present
@@ -22,10 +26,6 @@ selenium:
     - logo: "/images/sponsors/applitools.png"
       url: "https://applitools.com/"
       name: "Applitools"
-    # Sponsorship renewed October 16, 2024.
-    - logo: "/images/sponsors/lambda-test.png"
-      url: "https://www.lambdatest.com/selenium-automation?utm_source=selenium&utm_medium=open-source-sponsor&utm_campaign=nov_14&utm_term=sk&utm_content=web"
-      name: "LambdaTest"
     # Sponsorship start date: June 24, 2015, updated July 2023 (only logo, not the agreement)
     # - logo: "/images/sponsors/Digital.ai.jpg"
     #   url: "http://bit.ly/36uZ7ad"

website_and_docs/hugo.toml

@@ -164,8 +164,8 @@ plausible_analytics = true
 prism_syntax_highlighting = true
 
 # Enable announcement banner below navbar (Go to announcement-banner.html to change the message)
-banner_flag = false
-announcement_banner = false
+banner_flag = true
+announcement_banner = true
 
 # Enable Algolia DocSearch
 [params.search.algolia]

website_and_docs/layouts/partials/announcement-banner.html

@@ -4,12 +4,12 @@
 <section id="announcement-banner" class="alert-static g-0 row -bg-{{ $color }}">
   <div class="container g-0" style="padding: 10px;">
     <div class="row g-0 justify-content-center">
-      <div class="alert alert-{{ $color }} col-12 fade show mb-0 p-0 -bg-{{ $color }}" role="alert">
-          <h4 class="alert-heading text-center m-2">
-              Registrations Open for SeleniumConf 2025 | March 26–28 | Join Us In-Person!
-              <a href="https://seleniumconf.com/?utm_medium=Referral&utm_source=selenium.dev&utm_campaign=register" target='_blank' aria-pressed="true"> Register now!</a>
-          </h4>
-      </div>
+        <div class="alert alert-{{ $color }} col-12 fade show mb-0 p-0 -bg-{{ $color }}" role="alert">
+            <h4 class="alert-heading text-center m-2">
+                Tune in for the Selenium Community Live scheduled for April 25th, 2025. 
+                <a href="https://www.linkedin.com/events/seleniumcommunitylive-episode57315712465407733761/theater/" target='_blank' aria-pressed="true">Join us!</a>
+            </h4>
+        </div>
     </div>
   </div>
 </section>