chrome-extension resources should be properly supported via a browser-side URLLoaderFactory and hooked up to NavigationURLLoaderNetworkService and appropriate subresource bundles.
Seems like this will stick (woohoo!)
Still need component extension resources and content verification support, but I've filed separate bugs ( bug 782015 and bug 782025 ) for those.
This means extensions are mostly working as-is now. I can run chrome+NetworkService, navigate to the webstore, install some extensions, use them, etc. Remaining work apart from the above should be limited to porting internal uses of net::URLFetcher over to SimpleURLLoader.
Comment 1 by roc...@chromium.org
, Nov 1 2017