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
Using SeleniumBasic v2.0.9.0
Using ChromeDriver Version 117.0.5938.92
Chrome Browser Version 117.0.5938.132
Testing VBA Code:
Public chromebrowser As Selenium.WebDriver
Sub test()
Dim Button_click As Selenium.WebElement
Dim Findby As Selenium.By
Set chromebrowser= New Selenium.WebDriver
chromebrowser.Start "Chrome"
chromebrowser.Get "https://www.qoo10.sg/"
Set Findby = New Selenium.By
If Not chromebrowser.IsElementPresent(Findby.Css("#ul_pc_header_setting_info > li:nth-child(1) > a")) Then
Exit Sub
End If
Set Button_click = chromebrowser.FindElementByCss("#ul_pc_header_setting_info > li:nth-child(1) > a")
Button_click.Click
chromebrowser.Wait 500
End Sub
After the above code is executed, at the new page i.e. login screen, if user manually drag and drop any of the links i.e. 'a' tags will cause all the remaining 'a' tags to be broken. User unable to click any links after that.
This issue is only observed in Chrome v117.
The text was updated successfully, but these errors were encountered:
I confirmed that this is happening on my system as well - for both Chrome and Edge. I tried to set the "detach" browser capabilities option but could not get that to work in SeleniumBasic either. Sorry, no help here...
Thanks for the quick response and confirmation. I have also logged a defect at chrome release webpage. So I guess the only way is to wait if for Chrome developers to get it fixed?
Using SeleniumBasic v2.0.9.0
Using ChromeDriver Version 117.0.5938.92
Chrome Browser Version 117.0.5938.132
Testing VBA Code:
Public chromebrowser As Selenium.WebDriver
Sub test()
End Sub
After the above code is executed, at the new page i.e. login screen, if user manually drag and drop any of the links i.e. 'a' tags will cause all the remaining 'a' tags to be broken. User unable to click any links after that.
This issue is only observed in Chrome v117.
The text was updated successfully, but these errors were encountered: