Parse "purpose" member from Web 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 8e6ce266ef2e9fc53efbdec4ad9cca8aa6a508a6..98cd74f14f7a9fe768da32f5c5f8bf5cbf71b55e 100644
--- a/content/public/common/manifest.h
+++ b/content/public/common/manifest.h
@@ -27,6 +27,11 @@ struct CONTENT_EXPORT Manifest {
   // Structure representing an icon as per the Manifest specification, see:
   // http://w3c.github.io/manifest/#dfn-icon-object
   struct CONTENT_EXPORT Icon {
+    enum IconPurpose {
+      ANY = 0,
+      BADGE,
+    };
+
     Icon();
     Icon(const Icon& other);
     ~Icon();
@@ -46,6 +51,10 @@ struct CONTENT_EXPORT Manifest {
     // Empty if the parsing failed, the field was not present or empty.
     // The special value "any" is represented by gfx::Size(0, 0).
     std::vector<gfx::Size> sizes;
+
+    // Empty if the field was not present or not of type "string". Contains

[pkotwicz, 2016/10/18 14:13:56]

Nit: "Contains" -> "Defaults to"

[F, 2016/10/18 15:34:46]

Done.

+    // IconPurpose::ANY for all other parsing exceptions.
+    std::vector<IconPurpose> purpose;

[pkotwicz, 2016/10/18 14:13:56]

I think that "purposes" is a better name because "purposes" is a vector and can
contain many elements. I know that this conflicts with the spec.

Aside: The spec for "purposes" is only 2 months old. We could change "purpose"
to "purposes" in the spec if we wanted to.

[F, 2016/10/18 15:34:46]

I agree that "purposes" is a much better name. But I think for now we should
stay with the spec. We can update the naming after the spec is updated. WDYT?

[pkotwicz, 2016/10/18 17:16:12]

sounds good

   };
 
   // Structure representing a related application.