New issue
Advanced search Search tips

Issue 789574 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Jan 10
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Consider splitting chrome internals pages to a downloadable component

Project Member Reported by yfried...@chromium.org, Nov 29 2017

Issue description

I'm curious whether moving pages like about:sync, about:net, etc to an on-demand download the first time they're accessed would provide a significant win to our package distribution size. It's certainly the case that most users will never touch these and I believe they're non-trivial in size

First step is to investigate via supersize how big these resources are and then we can think about ways and whether it's worth offloading
 
Status: Archived (was: Untriaged)
Archiving P3s older than 1 year with no owner or component.

Sign in to add a comment