v1.9.2: better Selenium timeout logic
Important
Starting from this release Selenium session idle timeout works a bit differently. Session is now considered idle between the end of previous command and the start of the next command (previously idle time included command execution duration too). The most visible difference can be with page loading in the browser. Previously too slow page loading (sometimes caused by missing firewall rules) led to session timeout and broken tests. Now the same will run forever and should lead to test case timeout. This should allow to easily make distinction between too long idle time between Selenium commands and issues with system under test.