'goog:chromeOptions' 与量角器中的 chromeOptions 对比
'goog:chromeOptions' vs chromeOptions in Protractor
chromeOptions 似乎在某些时候被 'goog:ChromeOptions' 取代了。有谁知道这是什么时候改变的？我发现关于它的文档很少。
我 运行 针对 Selenium 网格版本进行了一些测试：elgalu/selenium:3.141.59-p41 使用 Chrome 81 和 Selenium 3.141.59 并注意到 w3c 标志不是在我将配置更改为使用 'goog:ChromeOptions' 之前没有得到尊重。
自 ChromeDriver v2.31 以来已更改。
因为这必须与W3C specification对齐。
摘录：
Remote ends may also introduce extension capabilities that are extra
capabilities used to provide configuration or fulfill other
vendor-specific needs. Extension capabilities’ key must contain a ":"
(colon) character, denoting an implementation-specific namespace. The
value can be arbitrary JSON types.
As with extension commands, it is suggested that the key used to
denote the extension capability namespace is based on the vendor
keywords listed in [CSS21] and precedes the first ":" character in the
string.
chromeOptions 似乎在某些时候被 'goog:ChromeOptions' 取代了。有谁知道这是什么时候改变的？我发现关于它的文档很少。
我 运行 针对 Selenium 网格版本进行了一些测试：elgalu/selenium:3.141.59-p41 使用 Chrome 81 和 Selenium 3.141.59 并注意到 w3c 标志不是在我将配置更改为使用 'goog:ChromeOptions' 之前没有得到尊重。
自 ChromeDriver v2.31 以来已更改。
因为这必须与W3C specification对齐。
摘录：
Remote ends may also introduce extension capabilities that are extra capabilities used to provide configuration or fulfill other vendor-specific needs. Extension capabilities’ key must contain a ":" (colon) character, denoting an implementation-specific namespace. The value can be arbitrary JSON types.
As with extension commands, it is suggested that the key used to denote the extension capability namespace is based on the vendor keywords listed in [CSS21] and precedes the first ":" character in the string.