New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 692716 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Cc:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug

Blocking:
issue 692706



Sign in to add a comment

webui resources should not contain 2x images

Project Member Reported by agrieve@chromium.org, Feb 15 2017

Issue description

Most images that are stored as 1x and 2x wind up living within chrome_100_percent.pak and chrome_200_percent.pak (and chrome_300_percent.pak)

It looks like https://cs.chromium.org/chromium/src/ui/webui/resources/webui_resources.grd is including these assets directly in resources.pak though.

This matters on Android because we purposefully don't ship the 2x variants in order to save space.
 

Comment 1 by dbeam@chromium.org, Feb 15 2017

Cc: dbeam@chromium.org agrieve@chromium.org
Labels: -Pri-3 Pri-2
Owner: ----
Status: Available (was: Assigned)
agrieve@: can you just wrap the 2x <includes> with <if expr="not android">?
Maybe... Do you know how I'd test this change? (e.g. navigate to X, which uses these resources?)

As an aside, are there any scripts that ensure we don't have unused resources in:
https://cs.chromium.org/chromium/src/ui/webui/resources/webui_resources.grd?

The compiler-warning-based unused resource stripper doesn't work when grit generates .cc files for resources.

Comment 3 by dbeam@chromium.org, Feb 28 2017

i don't really know how you'd test that your change didn't break something, but things might not compile if the resource is flattened (and it doesn't exist).

we probably don't have any scripts that look for unused resources in that file.
Labels: -binary-size Performance-Size

Comment 5 by wnwen@chromium.org, Sep 21 2017

Cc: wnwen@chromium.org
Project Member

Comment 6 by sheriffbot@chromium.org, Sep 24

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment