You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That list is not final, it is an example. It even states in the spec:
This list is not exhaustive.
When returning capabilities from New Session, it is valid to return a more specific platformName, allowing users to correctly identify the Operating System the WebDriver implementation is running on.
Thanks @lmtierney But either way I think there is something wrong in the method calls because, while I execute this scenario on WIN8 system the Java client is picking up XP, which is not correct. Where as Java Client intelligence does differentiates between Platform.WINDOWS, Platform.WIN8, Platform.WIN8_1 and Platform.WIN10
Selenium Grid uses platformName capability to find the best node for a new session.
Concrete drivers (like InternetExplorerDriver or FirefoxDriver) simply ignore this capability. They run a browser on the local machine, no matter what the current platform is.
platformName capability returned by a driver in the response to a new session request is totally unrelated to platformName capability passed to the driver constructor.
But, yes, XP is a wrong answer. It should be WINDOWS.
Selenium 3.5.3-Java-IEDriverServer 3.5.1 :
platformName
attribute returnsXP
where as W3C Specs mentions eitherlinux
,mac
orwindows
W3C Specs mentions the following:
In chapter 7. Capabilities, section 7.2 Processing Capabilities:
where as IEDriverServer 3.5.1 returns
XP
As per #4526 and this comment latest
IEDriverServer
is w3c compatible. But seems out of sync.Meta -
OS: Windows 8 Pro, 64 bit
Selenium Version: 3.5.3
Browser: Internet Explorer
Browser Version: 10.0 (64-bit)
Expected Behavior -
platformName
attribute should return eitherlinux
,mac
orwindows
Actual Behavior -
platformName
attribute returnsXP
Steps to reproduce -
Minimal Code Block :
Console Output :
Key : platformName Value :XP
The text was updated successfully, but these errors were encountered: