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
A large number of test cases related to the pdf of an automated testing infrastructure based on selenium cannot pass due to this issue.
At this time we are able to work around this by using the 133.0.3027.0 driver to operate the 134 browser.
We hope that this issue will be resolved before the release of the 135 browser, as it will be impossible to work around once the 135 browser is released.
Please help us with any investigation that is needed and we will do our best to assist you.
Thank you.
reproduction script
driver.windowHandles determines whether the number of output handles is two or one.
I can work around the ChromeDriver issue by fixing it and building it yourself. But I can't rebuild the EdgeDriver because it's not publicly available.
Does anyone have any good ideas?
What Happen
Two windowhandles are generated when a PDF tab is opened, and an error occurs when an operation is performed on the untethered windowhandle.
since when?
This has not occurred on 133.0.3027.0 EdgeDriver.
It occurs with 133.0.3028.0.
The same event is also occurring on the ChromeDriver side, for more details, please see
https://issues.chromium.org/u/2/issues/396611138?pli=1
What are you having trouble with?
A large number of test cases related to the pdf of an automated testing infrastructure based on selenium cannot pass due to this issue.
At this time we are able to work around this by using the 133.0.3027.0 driver to operate the 134 browser.
We hope that this issue will be resolved before the release of the 135 browser, as it will be impossible to work around once the 135 browser is released.
Please help us with any investigation that is needed and we will do our best to assist you.
Thank you.
reproduction script
driver.windowHandles determines whether the number of output handles is two or one.
The text was updated successfully, but these errors were encountered: