New issue
Advanced search Search tips

Issue 654995 link

Starred by 6 users

Issue metadata

Status: Assigned
Owner:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Task

Blocking:
issue 598069



Sign in to add a comment

Explore slimming Extensions system

Project Member Reported by ben@chromium.org, Oct 12 2016

Issue description

Post Content Modularization Project (issue 598069), there we should be able to reduce the amount of "extensions" code significantly. If we can rely on foundation services for package management, updating, instance management, Mojo for language bindings, and implement interfaces directly in core classes, much of the extensions infrastructure in the browser UI should dissolve. Extensions API code run in the renderer should be recast as a client library written in JS.
 

Comment 1 by jam@chromium.org, Apr 28 2017

Labels: -Pri-3 Pri-2
Owner: roc...@chromium.org
Tentatively assigning this to Ken.

Comment 2 by laforge@google.com, Nov 7 2017

Components: Internals>Services
Labels: Type-Task
Appending component Internals>Services to S13N projects and changing the Type (for tracking sake) to Type=Task.
Status: Assigned (was: Available)
Owner: rockot@google.com

Sign in to add a comment