- various Framework improvements
I just finished writing a complete list of improvements with descriptions, but when I submitted my post nothing was returned; I guess it timed-out.
One or more of the various updates may fix the previously reported problem. Unfortunately, I'm not able to confirm if the problem has been fixed because I'm not able to reproduce it. I can't even confirm there was a problem, but I'll keep testing none-the-less.

Why use the Chromium WebGadget over other options

1. No dependencies; works with or without WebView2 installed.
2. No worries about an abandon project; the Chromium WebGadget is not effected by changes to WebView2.
3. Most major browsers have adopted the Chrome DevTools Protocol, fully accessible from the Chromium WebGadget.
4. Can be used as a WebGadget or applied to any installed Chromium browser.
5. Can run in Headless Mode when applied to a Chromium browser.
6. Headless mode supports controlling any Chromium browser remotely.
7. There are a wide variety of examples including Progressive Web Apps (PWA) via ISAPI.
8. The WebSocket scripts are cross platform, used for accessing the Chrome DevTools Protocol.