The web app manifest object currently lives in content/public, with the ManifestParser in content/renderer (so it can talk to blink for some parsing work / run in the sandboxed process).
We'd like to move the manifest object itself to a component. The motivating driver is that we want to start caching icons from manifests in the FaviconService, which means that we need to have access to manifests within components/favicons/core (which does not depend on content). Additionally, componentising manifest means that we can reuse the object on iOS as well.
The ManifestParser would move directly into Blink and out of content/renderer in this process.
Mounir, do you have any thoughts / opinions on this proposal?
Comment 1 by fhorschig@google.com
, Mar 23 2017