OS: MacOS Sierra 10.12.6
Selenium Version: 3.5.2 (server)
Browser: Safari
Browser Version: TP 37
When I instantiate a RemoveWebDriver with safari options set to use TP, I expect to to launch a safari TP browser.
But the hub instantiates the stable safari browser 10.1.2.
Create a single node hub on MacOS with safari as browser. Launch a remote session with technologyPreview capability set to true.
After analysis, the bug seems to be located in ServicedSession where we do not pass any capabilities when creating the driver service.
Therefore, SafariDriverService will be instantiated with default SafariOptions. In consequence, The default Safari browser is used
Is there is some updates?
I have heard reports that this reproduces with the Selenium 3.6 jar as well. Can someone take a look? Happy to help however I can from the Safari side, but this is almost certainly a bug in grid-related code.
Partly related to #3123. Once that fix is in place, nodes should be able to be configured to always use the STP.
Also related to ed04104efdcc4ef201b37d1e7abb4f761b7e31d1, where we configure the service from the options passed to the remote driver.
Hi Simon, Kindly update once Selenium 3.7 beta has a fix for this - Thanks
The fix for this will be in 3.7
On Tue, Oct 24, 2017 at 4:11 AM, praveen-cimplicity <
[email protected]> wrote:
Hi Simon, Kindly update once Selenium 3.7 beta
https://www.seleniumhq.org/download/ has a fix for this - Thanks—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/SeleniumHQ/selenium/issues/4537#issuecomment-338859621,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABuRWC-ZE2hJ395nDDL8vUUWSDBYC2jks5svVVwgaJpZM4O-hl8
.
Thanks Simon for your efforts. Any 3.7 release cadence or ETA that selenium users can expect?
Version 3.7 has been shipped.
Just want to make sure the selenium 3 node JSON we are using for Technology preview is free from typos. Could someone please review and let me know in case of any issues? Thanks
{
"capabilities":
[
{
"browserName": "safari",
"maxInstances": 1,
"technologyPreview":true,
"seleniumProtocol": "WebDriver",
"webdriver.safari.driver": "/Applications/Safari Technology Preview.app/Contents/MacOS/safaridriver"
}
],
"proxy": "org.openqa.grid.selenium.proxy.DefaultRemoteProxy",
"maxSessions": 1,
"port": 5446,
"register": true,
"registerCycle": 5000,
"role": "node"
}
Hi Simon/Alexei,
Was this fix tested on a Remote Grid consisting of Safari Technology preview? Or was it tested locally?
Thanks
Praveen
Reading "technologyPreview" setting from the node config file is not yet implemented, it's an independent issue, we're working on this feature.
Hi Alexei, Could you please provide the GitHub issue# or link to track the issue for STP one? -Thanks