Changing SafeManifestParser to use the SafeXmlParser service.
Changing SafeManifestParser to use the SafeXmlParser service instead of having a dedicated Mojo interface for doing the parsing of extension manifests. SafeXmlParser parses the XML in a sandboxed process and returns a base::Value that can be traversed in the browser process. As a result, the mojom, traits, typemap files have been removed. The implementation of the parsing has been moved to safe_manifest_parser.cc. The update_manifest_unittest.cc was moved to safe_manifest_parser_unittest.cc and split into several tests (no changes to the logic). Bug: 786613 Change-Id: Ia586ea0e9689d45130013b6d4d992318eb9b7dc4 Reviewed-on: https://chromium-review.googlesource.com/777939 Commit-Queue: Jay Civelli <jcivelli@chromium.org> Reviewed-by:Tom Sepez <tsepez@chromium.org> Reviewed-by:
Ken Rockot <rockot@chromium.org> Reviewed-by:
Reilly Grant <reillyg@chromium.org> Cr-Commit-Position: refs/heads/master@{#520802}
Showing
Please register or sign in to comment