3 ms·
Maybe this could be approached by compiling the servo browser engine to wasm...
by manx 5y ago
Maybe this could be approached by compiling the servo browser engine to wasm...
- EvanAnderson 5y agoI'm shocked there _still_ isn't a browser-within-a-browser that renders to a canvas element "product" available yet. I've been expecting it for years. A cross-platform browser environment that prevents user control (no ad blockers, complete control of the "UX", no copy / pasting, no printing to PDF, etc) would be a hot seller to a particular kind of web property. Your existing development pipeline works (since you're still rendering to an HTML5 "browser") but you don't have to worry about users exerting any control over the experience. Throw some Widevine at it, some DNS-over-HTTPS-over-websockets with pinned certificates, and you've got a VM on most consumer-grade devices today that's completely outside user control. The users don't have to be tricked to install anything-- it'll run inside their existing browser on their PC, Mac, iOS device, Android device, ChromeOS device, etc. It's not "trusted computing" but it's close enough. This sounds completely awful, BTW, but I totally see it happening. Accessibility (and other minimum-viable-product features) are out there in permissively-licensed open source software just waiting to be integrated. It's only a matter of time. Nobody should make this, but somebody will succumb to the easy money and do it.