Creates the Suggestions UI

ios/chrome/browser/ui/suggestions/suggestions_item.h

Index: ios/chrome/browser/ui/suggestions/suggestions_item.h
diff --git a/ios/chrome/browser/ui/suggestions/suggestions_item.h b/ios/chrome/browser/ui/suggestions/suggestions_item.h
new file mode 100644
index 0000000000000000000000000000000000000000..1b6db3760eb25b8accc220dce863ef88033dc0af
--- /dev/null
+++ b/ios/chrome/browser/ui/suggestions/suggestions_item.h
@@ -0,0 +1,18 @@
+// Copyright 2016 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+#ifndef IOS_CHROME_BROWSER_UI_SUGGESTIONS_SUGGESTIONS_ITEM_H_
+#define IOS_CHROME_BROWSER_UI_SUGGESTIONS_SUGGESTIONS_ITEM_H_

[marq (ping after 24h), 2017/01/10 13:46:25]

Should this just be in a suggestions_item_actions.h file?

[gambard, 2017/01/10 14:50:35]

Done.

+
+// Protocol handling the actions sent in the responder chain by the suggestion
+// items.
+@protocol SuggestionsItemActions
+
+// Send through the responder chain when the button of a suggestion item is
+// pressed.
+- (void)buttonPressed;

[marq (ping after 24h), 2017/01/10 13:46:25]

An action should have a specific purpose and not be a generic UI event. For
example, the toolbar actions include -showToolsMenu: and hideToolsMenu: rather
than just -toolbarButtonPressed:. So should this be -addItem:? -addContentItem:?

For now I would also prefer that action methods by default use the
-(void)action:(id)sender signature, even though at the moment we don't heavily
rely on the |sender| parameter.

[gambard, 2017/01/10 14:50:35]

Done.

+
+@end
+
+#endif  // IOS_CHROME_BROWSER_UI_SUGGESTIONS_SUGGESTIONS_ITEM_H_