manifest: add theme_color value to the manifest

content/public/common/manifest.h

Index: content/public/common/manifest.h
diff --git a/content/public/common/manifest.h b/content/public/common/manifest.h
index 43bef5bee75f500d1233d3e80ba23a4a22c8e9c9..8fadf6e663aa8c74e366375d8b3e55fcfb22df4b 100644
--- a/content/public/common/manifest.h
+++ b/content/public/common/manifest.h
@@ -112,6 +112,10 @@ struct CONTENT_EXPORT Manifest {
   // or there is a parsing failure.
   bool prefer_related_applications;
 
+  // Set to kInvalidOrMissingThemeColor if parsing failed or field is not
+  // present.
+  int64_t theme_color;

[nasko, 2015/07/20 11:07:03]

I'm sorry I missed this earlier. Is there a reason why we are using 64bit value
here? It seems that the source of the data is 32bit and the value range is in
the 32bit space.

[Lalit Maganti, 2015/07/20 11:23:49]

Yes. The color is represented as an unsigned 32 bit integer but we need -1 to
represent a parsing issue. Unfortunately it causes a wastage of 31 bits but it
is the most elegant solution I can come up with.

+
   // This is a proprietary extension of the web Manifest, double-check that it
   // is okay to use this entry.
   // Null if parsing failed or the field was not present.
@@ -121,6 +125,9 @@ struct CONTENT_EXPORT Manifest {
   // IPC. The renderer process should truncate the strings before sending the
   // Manifest and the browser process must do the same when receiving it.
   static const size_t kMaxIPCStringLength;
+
+  // Constant representing an invalid theme color. Set to -1.
+  static const int64_t kInvalidOrMissingThemeColor;
 };
 
 } // namespace content