When executing tests on a fast machine, current expected condition dialogIsOpen might be returning true even though the dialog is still in transition. This can become a problem when trying to access element afterwards: they will be found in the DOM but due to the animation/transition still being in progress, selenium is not able to click on the item, resulting in test failure.

With this issue we should tackle the most prominent two cases: dialogs and tabs.

Thanks to mgeljic who has provided screenshots showing the various states of such a click, we can now provide locators and adjust/add expected conditions.

The status' are:

1. First tab is active
2. Click on second tab
3. Transition is ongoing and tab marked active
4. Tab marked active and transition done

As a result a tab can be considered open when it has the class active and when the app-preloader is gone from the DOM.