Initial commit of a basic Content Service
The Content Service is a new s13n project intended to servicify the bulk of the content layer's functionality, namely the ability for applications to embed navigable web content views backed by isolated, sandboxed content handlers. See https://tinyurl.com/ycrx5tgq for a high-level overview and (eventually) links to more detailed documentation. This CL lands a trivial client View API with some tiny mojom surface between it and the Content Service. The API as-is may be completely throw-away, but this change gets all the necessary boilerplate and plumbing landed. The ContentServiceDelegate and ContentViewDelegate C++ interfaces are exposed by the Content Service impl so that it can delegate to private src/content implementation details without a dependency on src/content. The browser itself is granted access to connect to Content Service for now so that basic integration testing can be done via content_browsertests. One such test is added here to verify a functioning end-to-end connection between a client's View instance and an actual backing WebContentsImpl. Bug: 854365 Change-Id: Idd8e4d0e5f2922ffc48686a4057e6e7c262c3cc3 Reviewed-on: https://chromium-review.googlesource.com/1107012 Commit-Queue: Ken Rockot <rockot@chromium.org> Reviewed-by:Tom Sepez <tsepez@chromium.org> Reviewed-by:
John Abd-El-Malek <jam@chromium.org> Cr-Commit-Position: refs/heads/master@{#569797}
Showing
services/content/BUILD.gn
0 → 100644
services/content/OWNERS
0 → 100644
services/content/service.cc
0 → 100644
services/content/service.h
0 → 100644
services/content/view_impl.h
0 → 100644
Please register or sign in to comment