CODEWITHSUNDEEP
seleniumprotractor
Scott Walter
Scott Walter

Reputation: 9512

'goog:chromeOptions' vs chromeOptions in Protractor

It seems at some point chromeOptions was replaced by 'goog:ChromeOptions'. Does anyone have an idea on when this was changed? I've found very little documentation on it.

I was running some tests against the Selenium grid version: elgalu/selenium:3.141.59-p41 which uses Chrome 81 and Selenium 3.141.59 and noticed w3c flag was not not being honored until I changed the config to use 'goog:ChromeOptions' instead.

Upvotes: 2

Views: 892

Answers (1)

Yevhen Laichenkov
Yevhen Laichenkov

Reputation: 8672

It has been changed since ChromeDriver v2.31.

Because this must be aligned with the W3C specification.

Excerpt:

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.

Upvotes: 1

Related Questions