Windows controller by the driver are using separate profiles, are non-interactive by default (don't respond to mouse events) etc. - all the things that Karma needs. Perhaps the launcher could use safaridriver jsut to launch Safari and use the regular socket.io-based communication once the connection is established?
This would eliminate some common issues with the launcher that rely on the fact that it doesn't create a separate profile (like #6).
Safari 10 added native WebDriver support: https://webkit.org/blog/6900/webdriver-support-in-safari-10/.
Windows controller by the driver are using separate profiles, are non-interactive by default (don't respond to mouse events) etc. - all the things that Karma needs. Perhaps the launcher could use safaridriver jsut to launch Safari and use the regular socket.io-based communication once the connection is established?
This would eliminate some common issues with the launcher that rely on the fact that it doesn't create a separate profile (like #6).