Consider splitting chrome internals pages to a downloadable component |
|
Issue descriptionI'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 |
|
►
Sign in to add a comment |
|
Comment 1 by benhenry@google.com
, Jan 10