> WebBundles Allow Sites to Evade Privacy and Security Tools I completely disagree. Browser-level code can still effectively apply user-defined privacy and sec

> WebBundles Allow Sites to Evade Privacy and Security Tools I completely disagree. Browser-level code can still effectively apply user-defined privacy and security policies onto WebBundles. Didn't Firefox originally solve the issue of deep-linking into opaque bundles with it's jar: URI scheme idea? For example, this URI could be used to reference specific files in a zip archive in Firefox. iirc this scheme might not be supported by Firefox anymore. jar://https://site.example/archive.zip!/file%201.txt The same concept could be applied for WebBundles with another similar URI scheme so that content blockers and security tools can effectively introspect the bundle before initializing resources from the bundle. For example, something like: bundle://[optional hash, origin, or regex?]![uri or regex] // e.g. bundle://https://site.example/!https://site.example/regulated-sub-bundle-file.html