Last year I looked at it and ran into a wall (for my usages at least); They had stripped all DOM manipulation via the Document Object. Back then the only "WebBrowser" interface (ShDocVw.dll >> ShellDocView AFAIR) seemed targeted
No way to get to the MsHTML Interfaces to manipulate the DOM directly: Which was my main mission years ago: Scanning and Tweaking the Document. Rick manipulates Chromium WebView2 directly and sometimes posts problems encountered there. My basic idea would be to call over a JS bridge, but that is just one of the pain points Rick mentions.
So yes, look at it if you need it, but be careful with promises based on prev experience. And PLEASE post about ways to make Chromium behave internally / tweak the DOM ;-)
