Send all of the icon URLs listed in Web Manifest to WebAPK Server.

chrome/android/webapk/libs/common/src/org/chromium/webapk/lib/common/WebApkConstants.java

Index: chrome/android/webapk/libs/common/src/org/chromium/webapk/lib/common/WebApkConstants.java
diff --git a/chrome/android/webapk/libs/common/src/org/chromium/webapk/lib/common/WebApkConstants.java b/chrome/android/webapk/libs/common/src/org/chromium/webapk/lib/common/WebApkConstants.java
index 53c2cb7926d8d91528425c43d0ac22f32a2cbdfb..bf5152d07de5390cc33353685089e026c1b3cc12 100644
--- a/chrome/android/webapk/libs/common/src/org/chromium/webapk/lib/common/WebApkConstants.java
+++ b/chrome/android/webapk/libs/common/src/org/chromium/webapk/lib/common/WebApkConstants.java
@@ -20,4 +20,8 @@ public final class WebApkConstants {
     public static final String EXTRA_SOURCE = "org.chromium.chrome.browser.webapp_source";
     public static final String EXTRA_WEBAPK_PACKAGE_NAME =
             "org.chromium.chrome.browser.webapk_package_name";
+
+    // We use ONE string to store all of the icon URLs in WebAPK's AndroidManifest.xml, and put a
+    // separator between them.
+    public static final String ICON_URL_SEPARATOR = "; ";

[pkotwicz, 2016/11/01 00:29:49]

Can the separator be just ' '?

I don't think that much is gained by making the separator "; " instead of " ".
Both
https://www.google.com/a b
https://www.google.com/a; b
are valid URLs

This CL puts a requirement on the WebAPK server to escape ' ' as %20
The WebAPK server should not do any other escaping. In particular, Chrome has
some very special handling for "https://www.google.com/%2%32"
Chrome escapes "https://www.google.com/%2%32" as "https://www.google.com/%2522"

[Xi Han, 2016/11/07 16:51:42]

We definitely could only use a space, since space is the only one that I find
shouldn't be in a valid URL. Yes, server will prepare such a metadata tag and
store it in the AndroidManifest.xml. Since Chrome canonicalizes all the URLs and
Serve just uses them and add a space between two icon URLs, we could handle it
correct when parsing the metadata.

 }