Other than #509, I don't think any of these should be blocking for your CL. (They're either editorial or out of scope.)
It looks like various people already shared their opinions on #509, so let's have that run its course.
The following revision refers to this bug:
https://chromium.googlesource.com/chromium/src.git/+/fb90fb92c0ce0e549112e9dfbeaeb2309aad883d
commit fb90fb92c0ce0e549112e9dfbeaeb2309aad883d
Author: zpeng <zpeng@chromium.org>
Date: Thu Feb 09 10:38:30 2017
Add "usages" field to Image in WebApk.proto
"usages" field is used by Chrome to specify intended usages for the image
sent in a WebAPK proto. An image can have multiple usages, e.g. "primary
icon" and "badge icon".
At most two images can have non-empty "usages" fields: the image most
suitable for primary icon, and the image most suitable for badge icon.
The "usages" field in the proto and manifest.icon.purpose defined in the W3C Web
Manifest specification are different.
- "usages" is used by Chrome to distinguish the image most suitable for primary
icon and the image most suitable for badge icon from other images, and from
each other.
- manifest.icon.purpose is used by Web developers to specify intended
usage for the images.
BUG= 649771
Review-Url: https://codereview.chromium.org/2686543002
Cr-Commit-Position: refs/heads/master@{#449255}
[modify] https://crrev.com/fb90fb92c0ce0e549112e9dfbeaeb2309aad883d/chrome/browser/android/webapk/webapk.proto
Comment 1 by pkotw...@chromium.org
, Sep 23 2016Owner: zpeng@chromium.org
Status: Assigned (was: Untriaged)