Edge version 112 latest update(4/7/2023) broke my webview2 devtools automation

Shivakumar thripurari 0

Edge version 112 latest update(4/7/2023) broke my webview2 devtools automation, it is able to get the remote session(webview2 app) of the browser but could not run JS on it. with latest Edge updates i should be able to run JS on the webview2 browser session, which is not working currently.

Yu Zhou-MSFT 12,951 Reputation points Microsoft Vendor

2023-04-17T08:55:59.32+00:00

Hi @Shivakumar thripurari

For WebView2 devtools automation, do you mean you're automating WebView2 apps with Edge WebDriver like what described in this doc? And how do you run JS on it?

Please provide a minimal code snippet which can run and reproduce the issue.
Shivakumar thripurari 0 Reputation points

2023-04-17T20:18:54.1933333+00:00

Yes, similarly but I am not using Selenium Edge webdriver, I have my own webdriver, basically it listen to the port 9222 and gets all remote sessions, and i will grab the one from it based on the url and run the JS on that session object, this is working on EDGE version 111 but not on 112 (after 4/7/2023 updates).
Yu Zhou-MSFT 12,951 Reputation points Microsoft Vendor

2023-04-18T09:23:52.5333333+00:00

Hi @Shivakumar thripurari

Is there any error message when it doesn't work? If possible, please provide minimal, reproducible code snippet so that we can have a test. Besides, for any feedback about WebView2, you can also report in the WebView2Feedback repo.

Shivakumar thripurari 0

Thanks Zhou for your response, There is no error message as such but when the code get executes to run JS on the webview2 browser session(used Websocket url to grab it) takes time and nothing happens on the browser.(set value to input element to login), it is using JS as command to following function. //command in my custom driver.cs file which runs the javascript command(window.GetJavaScriptMemberTempVariable = typeof $("input[id='username']:eq(0)", $("html"))[0];) this is working when i run it manually through edge console and returning 'object' result = this.BrowserInstance.Eval(javaScript, true); above line calls below function string strJSON = this.Eval(cmd, 300000, validateSession);

public string Eval(string cmd, int timeout = 300000, bool validateSession = true)
        {
            try
            {
                /** This will not work if navigation is done through document.location.
                 * For some reason Chrome will not update the session URL in that case.
                 */
                if (validateSession && this.LocationURL.ToLower() != this.LocationURLJS.ToLower())
                {
                    /** New session (navigate/redirect/etc) context is still loading. 
                     * Bypass this if you want to get the cached context.
                     */
                    return null;
                }
            }
            catch { }

            Dictionary<string, object> json_obj = new Dictionary<string, object>()
            {
                { "method", "Runtime.evaluate" },
                {
                    "params", new Dictionary<string, object>(){
                        { "expression", cmd },
                        { "objectGroup", "console" },
                        { "includeCommandLineAPI", true },
                        { "doNotPauseOnExceptions", false },
                        { "returnByValue", false },
                        { "timeout", timeout },
                    }
                },
                { "id", 1 },
            };

            var json = JsonConvert.SerializeObject(json_obj);
            return this.SendCommand(json);
        }

Please let me know if the latest Edge update CSP(content security policy) preventing evaluate command then how to bypass to run it.

Yu Zhou-MSFT 12,951 Reputation points Microsoft Vendor

2023-04-19T08:08:54.88+00:00

Hi @Shivakumar thripurari

I've tested the same scenario with Selenium Edge WebDriver but it works well in Edge version 112. I think there might be some issue with your own webdriver instead of Edge.

For Edge updating CSP, I haven't heard about this. You can also refer to Edge release notes.

Share via

Edge version 112 latest update(4/7/2023) broke my webview2 devtools automation