Summary
Add a provider to inspect WebView2 (embedded Chromium/Edge) DOM content hosted inside Win32/WinUI apps (README ""Future work""; also noted in docs/chromium-plugin.md).
Scope
- Detection: WebView2 runtime in the target (e.g.
EmbeddedBrowserWebView.dll and/or msedgewebview2.exe child processes).
- Reuse the CDP/DevTools approach from the existing Chromium plugin (
src/plugin_chromium/) but target the WebView2 DevTools endpoint.
- Graft the DOM subtree into the WebView2 host element in the Win32/WinUI tree.
Acceptance criteria
- DOM of a WebView2 control appears grafted under its host element.
- Handles the case where remote debugging isn't enabled (clear degradation).
Testing requirement: New framework providers/plugins must ship with a minimal sample app built with that UI framework (so the provider can be exercised end-to-end), plus automated tests. Follow the existing pattern (integration tests launch a real target app).
Filed as part of turning README/docs "Future work" into tracked issues. See docs/architecture.md and CONTRIBUTING.md (""Adding a new provider"") for conventions.
Summary
Add a provider to inspect WebView2 (embedded Chromium/Edge) DOM content hosted inside Win32/WinUI apps (README ""Future work""; also noted in
docs/chromium-plugin.md).Scope
EmbeddedBrowserWebView.dlland/ormsedgewebview2.exechild processes).src/plugin_chromium/) but target the WebView2 DevTools endpoint.Acceptance criteria
Testing requirement: New framework providers/plugins must ship with a minimal sample app built with that UI framework (so the provider can be exercised end-to-end), plus automated tests. Follow the existing pattern (integration tests launch a real target app).
Filed as part of turning README/docs "Future work" into tracked issues. See
docs/architecture.mdandCONTRIBUTING.md(""Adding a new provider"") for conventions.