Skip to content

Commit e29b748

Browse files
authored
Merge branch 'trunk' into csharp-selenium-manager-example
2 parents b801adf + 3084f59 commit e29b748

File tree

11 files changed

+106
-73
lines changed

11 files changed

+106
-73
lines changed

.github/workflows/dotnet-examples.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -85,7 +85,7 @@ jobs:
8585
distribution: 'temurin'
8686
java-version: 11
8787
- name: Run tests
88-
uses: nick-fields/[email protected].1
88+
uses: nick-fields/[email protected].2
8989
with:
9090
timeout_minutes: 20
9191
max_attempts: 3

.github/workflows/java-examples.yml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -58,7 +58,7 @@ jobs:
5858
run: keytool -import -noprompt -trustcacerts -alias SeleniumHQ -file examples/java/src/test/resources/tls.crt -keystore ${{ steps.java.outputs.path }}/lib/security/cacerts -storepass changeit
5959
- name: Run Tests Stable
6060
if: matrix.release == 'stable'
61-
uses: nick-invision/[email protected].1
61+
uses: nick-invision/[email protected].2
6262
with:
6363
timeout_minutes: 40
6464
max_attempts: 3
@@ -67,7 +67,7 @@ jobs:
6767
mvn -B test -D"jdk.internal.httpclient.disableHostnameVerification=true"
6868
- name: Run Tests Nightly Linux/macOS
6969
if: matrix.release == 'nightly' && matrix.os != 'windows'
70-
uses: nick-invision/[email protected].1
70+
uses: nick-invision/[email protected].2
7171
with:
7272
timeout_minutes: 40
7373
max_attempts: 3
@@ -81,7 +81,7 @@ jobs:
8181
8282
- name: Run Tests Nightly Windows
8383
if: matrix.release == 'nightly' && matrix.os == 'windows'
84-
uses: nick-invision/[email protected].1
84+
uses: nick-invision/[email protected].2
8585
with:
8686
timeout_minutes: 40
8787
max_attempts: 3

.github/workflows/js-examples.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -116,7 +116,7 @@ jobs:
116116
env:
117117
NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
118118
- name: Run tests
119-
uses: nick-invision/[email protected].1
119+
uses: nick-invision/[email protected].2
120120
with:
121121
timeout_minutes: 20
122122
max_attempts: 3

.github/workflows/kotlin-examples.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -83,7 +83,7 @@ jobs:
8383
distribution: 'temurin'
8484
java-version: 11
8585
- name: Run tests
86-
uses: nick-invision/[email protected].1
86+
uses: nick-invision/[email protected].2
8787
with:
8888
timeout_minutes: 20
8989
max_attempts: 3

.github/workflows/python-examples.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -95,7 +95,7 @@ jobs:
9595
distribution: 'temurin'
9696
java-version: 11
9797
- name: Run tests
98-
uses: nick-invision/[email protected].1
98+
uses: nick-invision/[email protected].2
9999
with:
100100
timeout_minutes: 60
101101
max_attempts: 3

.github/workflows/ruby-examples.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -84,7 +84,7 @@ jobs:
8484
distribution: 'temurin'
8585
java-version: 11
8686
- name: Run tests
87-
uses: nick-invision/[email protected].1
87+
uses: nick-invision/[email protected].2
8888
with:
8989
timeout_minutes: 20
9090
max_attempts: 3

examples/dotnet/SeleniumDocs/SeleniumDocs.csproj

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,8 +10,8 @@
1010
<PackageReference Include="Microsoft.IdentityModel.Tokens" Version="7.7.1" />
1111
<PackageReference Include="MSTest.TestAdapter" Version="3.6.0" />
1212
<PackageReference Include="MSTest.TestFramework" Version="3.6.0" />
13-
<PackageReference Include="Selenium.Support" Version="4.28.0" />
14-
<PackageReference Include="Selenium.WebDriver" Version="4.28.0" />
13+
<PackageReference Include="Selenium.Support" Version="4.29.0" />
14+
<PackageReference Include="Selenium.WebDriver" Version="4.29.0" />
1515
</ItemGroup>
1616

1717
<ItemGroup>

examples/kotlin/pom.xml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@
1212
<kotlin.version>2.1.0</kotlin.version>
1313

1414
<slf4j.version>2.0.16</slf4j.version>
15-
<logback.version>1.5.16</logback.version>
15+
<logback.version>1.5.17</logback.version>
1616

1717
<junit5.version>5.12.0</junit5.version>
1818
<wdm.version>5.2.3</wdm.version>
Lines changed: 38 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: "BiDirectional functionality"
2+
title: "双向功能"
33
linkTitle: "BiDi"
44
weight: 16
55
aliases: [
@@ -12,23 +12,27 @@ aliases: [
1212
]
1313
---
1414

15-
BiDirectional means that communication is happening in two directions simultaneously.
16-
The traditional WebDriver model involves strict request/response commands which only allows for communication to
17-
happen in one direction at any given time. In most cases this is what you want; it ensures that the browser is
18-
doing the expected things in the right order, but there are a number of interesting things that can be done with
19-
asynchronous interactions.
2015

21-
This functionality is currently available in a limited fashion with the [Chrome DevTools Protocol] (CDP),
22-
but to address some of its drawbacks, the Selenium team, along with the major
23-
browser vendors, have worked to create the new [WebDriver BiDi Protocol](https://w3c.github.io/webdriver-bidi/).
24-
This specification aims to create a stable, cross-browser API that leverages bidirectional
25-
communication for enhanced browser automation and testing functionality,
26-
including streaming events from the user agent to the controlling software via WebSockets.
27-
Users will be able to listen for and record or manipulate events as they happen during the course of a Selenium session.
16+
双向是指通信同时在两个方向上进行.
17+
传统的 WebDriver 模型涉及严格的请求/响应命令,
18+
在任何时候都只允许单向通信.
19+
在大多数情况下, 这正是您想要的;它能确保浏览器以正确的顺序执行预期的操作,
20+
但异步交互也有许多有趣的地方.
2821

29-
### Enabling BiDi in Selenium
3022

31-
In order to use WebDriver BiDi, setting the capability in the browser options will enable the required functionality:
23+
目前, [Chrome DevTools Protocol] (CDP) 可以有限地提供这种功能,
24+
但为了解决它的一些缺点,
25+
Selenium 团队与主要浏览器供应商一起创建了新的 [WebDriver BiDi 协议](https://w3c.github.io/webdriver-bidi/).
26+
该规范旨在创建一个稳定的跨浏览器 API,
27+
利用双向通信增强浏览器自动化和测试功能、
28+
包括通过 WebSockets 从用户代理到控制软件的流式事件.
29+
用户将能在 Selenium 会话过程中监听、记录或操作事件.
30+
31+
32+
### 在Selenium中启用 BiDi
33+
34+
为了使用 WebDriver BiDi,
35+
在浏览器选项中设置该功能将启用所需的功能:
3236

3337
{{< tabpane langEqualsHeader=true >}}
3438
{{< tab header="Java" >}}
@@ -51,17 +55,25 @@ options.setCapability("webSocketUrl", true);
5155
{{< /tab >}}
5256
{{< /tabpane >}}
5357

54-
This enables the WebSocket connection for bidirectional communication,
55-
unlocking the full potential of the WebDriver BiDi protocol.
5658

57-
Note that Selenium is updating its entire implementation from WebDriver Classic to WebDriver BiDi (while
58-
maintaining backwards compatibility as much as possible), but this section of documentation focuses on the new
59-
functionality that bidirectional communication allows.
60-
The low-level BiDi domains will be accessible in the code to the end user, but the goal is to provide
61-
high-level APIs that are straightforward methods of real-world use cases. As such, the low-level
62-
components will not be documented, and this section will focus only on the user-friendly
63-
features that we encourage users to take advantage of.
6459

65-
If there is additional functionality you'd like to see, please raise a
66-
[feature request](https://github.com/SeleniumHQ/selenium/issues/new?assignees=&labels=&template=feature.md).
60+
这将启用用于双向通信的 WebSocket 连接、
61+
释放 WebDriver BiDi 协议的全部潜能.
62+
63+
64+
65+
请注意, Selenium 正在将其整个实现从 WebDriver Classic
66+
升级到 WebDriver BiDi (同时尽可能保持向后兼容性) ,
67+
但本部分文档的重点是双向通信所允许的新功能.
68+
69+
70+
71+
终端用户可以在代码中访问低级 BiDi 域,
72+
但我们的目标是提供高级应用程序接口,
73+
这些应用程序接口是真实世界用例的直接方法.
74+
因此, 我们将不对底层组件进行记录, 本节将只关注我们鼓励使用者利用的用户友好功能.
75+
76+
77+
如果您希望看到其他功能, 请提出
78+
[功能请求](https://github.com/SeleniumHQ/selenium/issues/new?assignees=&labels=&template=feature.md).
6779

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

Lines changed: 53 additions & 36 deletions
Original file line numberDiff line numberDiff line change
@@ -1,31 +1,34 @@
11
---
2-
title: "IE specific functionality"
2+
title: "IE 特定功能"
33
linkTitle: "Internet Explorer"
44
weight: 8
55
description: >-
6-
These are capabilities and features specific to Microsoft Internet Explorer browsers.
6+
这些是 Microsoft Internet Explorer 浏览器特有的功能和特性.
77
aliases: [
88
"/zh-cn/documentation/capabilities/internet_explorer"
99
]
1010
---
1111

12-
As of June 2022, Selenium officially no longer supports standalone Internet Explorer.
13-
The Internet Explorer driver still supports running Microsoft Edge in "IE Compatibility Mode."
12+
自2022年6月起, Selenium 正式不再支持独立的 Internet Explorer.
13+
Internet Explorer 驱动程序仍支持在 "IE 兼容模式" 下运行 Microsoft Edge.
1414

15-
## Special considerations
15+
## 特别注意事项
1616

17-
The IE Driver is the only driver maintained by the Selenium Project directly.
18-
While binaries for both the 32-bit and 64-bit
19-
versions of Internet Explorer are available, there are some
20-
[known limitations](//jimevansmusic.blogspot.co.uk/2014/09/screenshots-sendkeys-and-sixty-four.html)
21-
with the 64-bit driver. As such it is recommended to use the 32-bit driver.
17+
IE 驱动程序是 Selenium 项目直接维护的唯一驱动程序.
18+
虽然 32 位和 64 位版本的版本的二进制文件,
19+
但有一些64位驱动程序的
20+
[已知限制](//jimevansmusic.blogspot.co.uk/2014/09/screenshots-sendkeys-and-sixty-four.html).
21+
因此, 建议使用 32 位驱动程序.
2222

23-
Additional information about using Internet Explorer can be found on the
24-
[IE Driver Server page]({{< ref "/documentation/ie_driver_server/" >}})
23+
有关使用 Internet Explorer 的其他信息, 请参见
24+
[IE 驱动程序服务器页面]({{< ref "/documentation/ie_driver_server/" >}})
2525

26-
## Options
26+
## 选项
27+
28+
在 Internet Explorer 兼容模式下启动 Microsoft Edge 浏览器,
29+
并使用基本定义的选项,
30+
看起来就像这样:
2731

28-
Starting a Microsoft Edge browser in Internet Explorer Compatibility mode with basic defined options looks like this:
2932

3033
{{< tabpane text=true >}}
3134
{{< tab header="Java" >}}
@@ -48,13 +51,14 @@ Starting a Microsoft Edge browser in Internet Explorer Compatibility mode with b
4851
{{< /tab >}}
4952
{{< /tabpane >}}
5053

51-
As of Internet Explorer Driver v4.5.0:
52-
* If IE is not present on the system (default in Windows 11), you do not need to
53-
use the two parameters above. IE Driver will use Edge and will automatically locate it.
54-
* If IE and Edge are both present on the system, you only need to set attaching to Edge,
55-
IE Driver will automatically locate Edge on your system.
5654

57-
So, if IE is not on the system, you only need:
55+
截至 Internet Explorer 驱动程序 v4.5.0:
56+
* 如果系统中没有 IE(Windows 11 中的默认设置), 则无需使用上述两个参数.
57+
使用上述两个参数.IE 驱动程序将使用 Edge, 并自动对其进行定位.
58+
* 如果系统上同时存在 IE 和 Edge, 则只需设置附加到 Edge、
59+
IE 驱动程序将自动在系统中定位 Edge.
60+
61+
因此, 如果系统中没有 IE, 您只需要:
5862

5963
{{< tabpane langEqualsHeader=true >}}
6064
{{< tab header="Java" text=true >}}
@@ -82,7 +86,8 @@ val driver = InternetExplorerDriver(options)
8286
{{< /tab >}}
8387
{{< /tabpane >}}
8488

85-
Here are a few common use cases with different capabilities:
89+
90+
以下是几种具有不同功能的常见用例:
8691

8792
### fileUploadDialogTimeout
8893

@@ -125,7 +130,7 @@ val driver = RemoteWebDriver(options)
125130
此功能将清除InternetExplorer所有正在运行实例的
126131
_缓存, 浏览器历史记录和Cookies_
127132
(包括手动启动或由驱动程序启动的实例) .
128-
默认情况下此设置为 `false`.
133+
默认情况下, 此设置为 `false`.
129134

130135
使用此功能将导致启动浏览器时性能下降,
131136
因为驱动程序将等待直到缓存清除后再启动IE浏览器.
@@ -216,7 +221,7 @@ val driver = RemoteWebDriver(options)
216221
但是, 到目前为止,
217222
这仍然是第二好的选择,
218223
并且第一选择应该 *始终* 是手动实际设置每个区域的保护模式设置.
219-
如果用户正在使用此属性
224+
如果用户正在使用此属性,
220225
则只会给予 "尽力而为" 的支持.
221226

222227
此功能接受一个布尔值作为参数.
@@ -495,18 +500,22 @@ fun main() {
495500

496501

497502

498-
## Service
503+
## 服务
499504

500-
Service settings common to all browsers are described on the [Service page]({{< ref "../drivers/service.md" >}}).
505+
[Service page]({{< ref "../drivers/service.md" >}})
506+
描述了所有浏览器通用的服务设置.
501507

502-
### Log output
508+
### 日志输出
503509

504-
Getting driver logs can be helpful for debugging various issues. The Service class lets you
505-
direct where the logs will go. Logging output is ignored unless the user directs it somewhere.
510+
获取驱动程序日志有助于调试各种问题.
511+
服务类可让您指示日志的去向.
512+
除非用户指定了日志输出的位置,
513+
否则日志输出将被忽略.
506514

507-
#### File output
515+
#### 文件输出
516+
517+
更改日志输出以保存到特定文件:
508518

509-
To change the logging output to save to a specific file:
510519

511520
{{< tabpane text=true >}}
512521
{{% tab header="Java" %}}
@@ -534,9 +543,12 @@ Property value: String representing path to log file
534543
{{< /tab >}}
535544
{{< /tabpane >}}
536545

537-
#### Console output
546+
#### 控制台输出
547+
548+
549+
要更改日志输出, 使其在控制台中显示为标准输出:
550+
538551

539-
To change the logging output to display in the console as STDOUT:
540552

541553
{{< tabpane text=true >}}
542554
{{% tab header="Java" %}}
@@ -565,9 +577,12 @@ Property value: `DriverService.LOG_STDOUT` or `DriverService.LOG_STDERR`
565577
{{< /tab >}}
566578
{{< /tabpane >}}
567579

568-
### Log Level
569-
There are 6 available log levels: `FATAL`, `ERROR`, `WARN`, `INFO`, `DEBUG`, and `TRACE`
570-
If logging output is specified, the default level is `FATAL`
580+
581+
### 日志级别
582+
有 6 种可用的日志级别:`FATAL``ERROR``WARN``INFO``DEBUG``TRACE`
583+
如果指定了日志输出, 默认级别为`FATAL`.
584+
585+
571586

572587
{{< tabpane text=true >}}
573588
{{% tab header="Java" %}}
@@ -594,7 +609,9 @@ Property value: String representation of `InternetExplorerDriverLogLevel.DEBUG.t
594609
{{< /tab >}}
595610
{{< /tabpane >}}
596611

597-
### Supporting Files Path
612+
613+
### 辅助文件路径
614+
598615

599616
{{< tabpane text=true >}}
600617
{{< tab header="Java" >}}

0 commit comments

Comments
 (0)