Need to wait for https://github.com/SeleniumHQ/selenium/issues/17355 to be fixed, actually. It's of course possible to workaround this problem, but let's see if it's fixed quickly first.
