294381 2025-06-12 03:09:35 -0700 Add WebViewAssetLoader‐style API to WKWebView for virtual HTTPS asset hosting 2026-01-18 14:52:30 -0800 1 1 1 Unclassified WebKit WebCore Misc. WebKit Nightly Build Unspecified Unspecified NEW InRadar P2 Enhancement --- 1 dev.satoshi.1016 webkit-unassigned achristensen annevk beidson cdumez webkit-bug-importer oldest_to_newest 2123236 0 dev.satoshi.1016 2025-06-12 03:09:35 -0700 **Background** On Android’s Chromium‐based WebView, the WebViewAssetLoader API lets apps serve bundled assets (from `assets/` or `res/`) under a virtual HTTPS domain (e.g. `https://appassets.androidplatform.net/`) without needing real TLS certificates. JavaScript in the page sees a proper HTTPS origin, so `fetch()`/XHR and CORS behave as if loading from a remote server. WKWebView today lacks an equivalent. Developers must either run a local HTTP server or use custom URL schemes, neither of which fully emulates an HTTPS origin. **Feature Request** Introduce a WebKit API—analogous to Android’s WebViewAssetLoader—that allows configuration of a virtual HTTPS hostname for serving app‐bundled resources. 2124694 1 webkit-bug-importer 2025-06-19 03:10:14 -0700 <rdar://problem/153812992> 2146093 2 dev.satoshi.1016 2025-09-26 00:40:59 -0700 Hi WebKit team—could you share the current status or triage outcome for this request? I can’t access the linked Radar (rdar://problem/153812992), so any public note here would help. If it’s tracked elsewhere, please feel free to mark this as a duplicate or close with a public pointer. Thank you! 2172810 3 dev.satoshi.1016 2026-01-18 01:51:19 -0800 It doesn't look like anyone is actively working on this issue at the moment, so I'd like to take a shot at it. 2172875 4 beidson 2026-01-18 14:52:30 -0800 > It doesn't look like anyone is actively working on this issue at the moment, so I'd like to take a shot at it. While you're quite free to work on a patch, please note that changes to the public API that a particular vendor ships are entirely up to that vendor. And if that vendor does not want a particular API exposed, they are under no obligation to expose it. i.e. If your goal is to add WKWebView API and have it end up in an actual macOS/iOS/visionOS SDK, that's not actually up to the WebKit open source project.