You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 18, 2019. It is now read-only.
The code inclose.js assumes order is the order of creation and [0] is the "original" tab, this is not true and can cause race conditions when closing a new tab that is presented at [0] in the "windowsHandles()" return.
Environment (please complete the following information):
WebdriverIO version: 4.14.3
Mode: N/A
If WDIO Testrunner, running sync/async: N/A
Node.js version: N/A
NPM version: N/A
Browser name and version: IE 11
Platform name and version: macOS (Mojave)
Additional wdio packages used (if applicable): Lots
Config of WebdriverIO
N/A
Describe the bug
IE doesn't return tabs/windows in the order created this will cause issues with places that assume order (i.e. close.js)
To Reproduce
Not exactly easy as we need to wait for IE to give back the tabs in different orders
Expected behavior
A clear and concise description of what you expected to happen.
From @mikesalvia on February 8, 2019 16:2
The code in
close.js
assumes order is the order of creation and [0] is the "original" tab, this is not true and can cause race conditions when closing a new tab that is presented at [0] in the "windowsHandles()" return.Environment (please complete the following information):
Config of WebdriverIO
N/A
Describe the bug
IE doesn't return tabs/windows in the order created this will cause issues with places that assume order (i.e.
close.js
)To Reproduce
Not exactly easy as we need to wait for IE to give back the tabs in different orders
Expected behavior
A clear and concise description of what you expected to happen.
Log
N/A
Additional context
N/A
Copied from original issue: webdriverio/webdriverio#3531
The text was updated successfully, but these errors were encountered: