@BeyondEvil could you have a look at this? Should be quite trivial.

Thanks! I'm planning on putting in some time during the weekend to look at all open issues and PRs.

Please rebase. Thanks.

@ssbarnea I’ve rebased my branch.

Darn it, I am the third person to create this pr [#298, after #287] with mildly different tests. @BeyondEvil - any way to review/merge this?

Related to #265. [now it's cross-linked to the issue and maybe a fourth person won't write it :).]

cc: @ssbarnea

Sorry for not getting to this sooner @christiansandberg

tl;dr had spine surgery which led to complications.

Anyway, as soon as I'm satisfied with understanding the issue this is fixing (just want to see it with my own eyes) I'm going to merge this.

@dhalperi Sorry you had to do all that work, but you should've checked existing issues and PRs amirite 😉 What I would like for you to do, once this is merged, is to rebase. What will be left is basically that extra test (which is awesome!) but I also want you to update CHANGES.rst and give yourself and Christian credit. 😄For version you can just bump the patch number and for date put unreleased.

All good?

@BeyondEvil - your health takes top priority, I hope you're doing okay now. Glad to see you are able to work again. Everyone's having a different thing happening in this crazy time...

I am happy to support in whatever mode is best! Let me know. (Also, if there's a gitter or slack channel that. might better facilitate realtime communication, I can go there)

I'm jimboslice in the official SeleniumHQ slack @dhalperi :)

@BeyondEvil - the official selenium slack HQ link (from here) has expired - maybe someone there should refresh it. The question I came in to ask - will it be possible to make a new release with this fix sometime soon?