I am getting the same thing here.
It looks likes Chrome updates have broken some Selenium behavior.  I have
no time to look at this in any detail for the next several weeks, however.

Karl
On Wed, Jul 11, 2018 at 10:30 AM Irindu Nugawela <[EMAIL PROTECTED]>
wrote: