Remove safari-only restriction for browserName capability #127
This means existing Selenium Grid -> Appium node configurations using
Removing the specific
I've tested this with Appium v1.5.1 and Selenium Grid 2.52.0. Will follow-up for
I noticed the stuck build was cancelled, so I triggered a new build with some empty commits, I'm getting the keyboard test failing:
This change should not affect that at all. Should I push another commit to trigger another build?
This restriction broke compatibility with Selenium Grid where the browserName capability is used to define the node's available simulator/devices.