Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Did Edge version 119 break SeleniumBasic? #276

Open
JoshSavage17 opened this issue Nov 17, 2023 · 1 comment
Open

Did Edge version 119 break SeleniumBasic? #276

JoshSavage17 opened this issue Nov 17, 2023 · 1 comment

Comments

@JoshSavage17
Copy link

I use VBA/SeleniumBasic/Edge to automate several files. A couple weeks ago I was on version 118 of Edge/Edge Driver and everything worked. I came to work on a Monday and had Edge version 119. Updated the Edge Driver to match, 119.0.2151.44. Since then both Edge/Driver have been updated to 119.0.2151.58, and again to 119.0.2151.72 as of today, and get the same error. The section of code it's getting hung up on is the maximizing of the window.

Version: SeleniumBasic-2.0.9.0 Updated to Edge/Driver version 119.0.2151.72

The error:

Run-time error '23':

NoSuchWindowError
Window not found: no such window: target window already closed
from unknown error: web view not found
(Session info: MicrosoftEdge = 119.0.2151.58)
(Driver info: msedgedriver = 119.0.2151.58
(33e26e7eb4fba096f2f29de91f90d34b8597be96),platform=Windows NT 10.0.19045 x86_64)
Visually what happens: Small box opens to select username (handled by SetCapability so it goes away automatically.) Edge window opens and shows a message that the user was selected. The mouse moves to click OK on the message box Error with code when attempting to maximize the window. The Edge window remains open until/unless the module is ended.

The code:

Set oEdgeObject= CreateObject("Selenium.EdgeDriver")
With oEdgeObject

On Error GoTo SiteHandler

    .SetCapability "ms:edgeOptions", "{""excludeSwitches"":[""enable-automation""]}"
    .Start
    .Wait 1000

    Call LeftClick(600, 400)
    .Wait 1000
    
    .Window.Maximize

Attempted things:
Not using the SetCapability line to automatically select a profile.
Used SwitchToNextWindow (causes error, window does not exist)
Used SwitchToPreviousWindow (does not cause an error but does not resolve error either. Tried using it multiple times just in case it thought it was several windows again... didn't work.)
Tested code, as is, on another computer that still has Edge version 118
Attempted to use .get with and without the SetCapability. The SetCapability automatically logs in, and when I manually select the profile it does the same thing. Opens up a normal looking Edge window and says X user has logged in, and gives the same error. Attempted to use get without SetCapability and without selecting a profile manually. Clicking F8 through to the .get command opened the website in the small pseudo-Edge window. The window cannot be maximized and doesn't have an address bar, and I assume lacks multiple other things. Unfortunately I'm too new to be able to post an image. By default I have a variable that fills out with a website based on which module I'm running. I've tried manually filling the variable out with the Google address. Same result each time.

Goal: Open Edge, with current user/Edge profile, maximize the window, execute the rest of the code.

@ironsand-sou-eu
Copy link

This has been a big problem in chrome also. I have an application, and at each browser update it was needed to update the chromedriver version (you probably experience the same with the edgedriver).

Since chromedriver started to be integrated with Chrome for Testing versions, it has been a nightmare to find the correct version. Since around the 119/120, it was, more precisely, impossible in some versions (the subversions were incompatible), and the application just needed to wait for the next version. Right now, in the 123.0.6312.58, even the correct version doesn't work...

I refactored one of my applications, from VBA/Selenium Basic to a Typescript Chrome extension, to avoid this issue, and I'll need to do it with the other two.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants