Skip to content

Qualify native WebView providers and correct navigation and teardown - #1

Open
bytetroll wants to merge 13 commits into
masterfrom
codex/webview-platform-qualification
Open

bytetroll wants to merge 13 commits into
masterfrom
codex/webview-platform-qualification

Conversation

@bytetroll

@bytetroll bytetroll commented Nov 13, 2026 •

Copy link
Copy Markdown
Contributor

Completes source qualification of the Matrix WebView profile on GTK4/WebKitGTK, Win32/WebView2 and AppKit/WKWebView. The public API provides explicit provider selection, hidden-window creation, readiness, showing, navigation, HTML, synchronous JavaScript function evaluation, copied events, page messages and closure. Native message provenance remains capability-based; the migration table explicitly lists deferred legacy APIs.

The providers now preserve DOM/JavaScript state during fragment navigation and complete repeated fragments idempotently. Windows authorizes the exact initial document request before network dispatch, preserves valid HTTP error documents, and drains private profiles even when a window closes during asynchronous initialization. Retirement is published before native teardown can reenter an aborted callback. Bounded operation, process, profile and source-integrity checks remain enforced.

Validation at head 63d3e49d953179c81231402cf07dc7d6dbe17939, tested PR merge 7b624bae6c22e35e8049db7366340e3d732ec2f8, with framework e7bc2a00e6854084b7b5084e29fa50456cbe8977:

  • All four platform jobs passed: Linux x86-64, Windows x86-64, Intel macOS and Apple Silicon macOS. Every artifact was independently replayed against its manifest and exact test inventory.
  • Each host passed seven exact contract suites (57 runtime, 28 WebView ABI, 40 UI ABI, 216 formatted-text, 392 markup, 209 shared-provider and 36 JavaScript checks), four synthetic routes and four real-browser routes: textual NIL, binary NIL, AOT and JIT.
  • Every browser route passed all 17 groups, including an initial URL with a fragment, changed/repeated fragments, copied messages, exceptions, explicit redirect follow, HTTP 404 documents and immediate window closure. The owned server observed exactly one initial page, redirect, explicit follow and error-document request per route.
  • All 14 owned commands, the HTTP fixture and private profiles cleaned up. No unexpected owned descendants remained. Source, toolchain, standard-library and copied-provider seals were unchanged. Linux restored its complete AppArmor inventory; Windows restored the selected runner telemetry/tool settings.
  • Actual engines: GTK 4.14.5 / WebKitGTK 2.52.6; WebView2 runtime 131.0.2903.86 (separate SDK 1.0.4314.35); system WKWebView on macOS 15.7.9 Intel and 15.8.2 ARM.
  • Secrets and path audit passed, including full fetched history and the current tree. The public repository retains matching platform/audit checks and independent-review protections.

README and platform documentation describe the implemented profile, reproducible qualification and precise limits. This qualifies source consumers, not a published or activated SDK. The reviewed framework bridge is being consolidated onto current master in exec-software/exec-nil-framework#41. No SDK activation or release deployment is included.

@bytetroll bytetroll changed the title Qualify browser providers on isolated hosted runners Qualify native WebView providers and correct navigation and teardown Nov 13, 2026
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

Successfully merging this pull request may close these issues.

1 participant