Index: ios/clean/chrome/browser/ui/commands/dialog_commands.h |
diff --git a/ios/clean/chrome/browser/ui/commands/dialog_commands.h b/ios/clean/chrome/browser/ui/commands/dialog_commands.h |
new file mode 100644 |
index 0000000000000000000000000000000000000000..1e602e6061bcd8daaa3f1d528f20b0e9df04bab2 |
--- /dev/null |
+++ b/ios/clean/chrome/browser/ui/commands/dialog_commands.h |
@@ -0,0 +1,20 @@ |
+// Copyright 2017 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_CLEAN_CHROME_BROWSER_UI_COMMANDS_DIALOG_COMMANDS_H_ |
+#define IOS_CLEAN_CHROME_BROWSER_UI_COMMANDS_DIALOG_COMMANDS_H_ |
+ |
+// Command protocol for dismissing DialogConsumers. |
+@protocol DialogDismissalCommands |
marq (ping after 24h)
2017/06/14 10:52:14
Maybe just -DialogCommands, so if (as seems likely
kkhorimoto
2017/06/23 06:24:17
I don't think there will be a |-showDialog| comman
|
+ |
+// Called to dismiss the dialog. |buttonTag| is the tag of the DialogButtonItem |
marq (ping after 24h)
2017/06/14 10:52:14
Commands shouldn't presume a particular UI impleme
kkhorimoto
2017/06/23 06:24:17
I changed tag to identifier and updated the commen
|
+// corresponding to the button that dismissed the dialog, or nil if dismissed |
+// programmatically. |inputStrings| are the text field values, and are returned |
+// in the same order as the text field items were provided to the consumer. |
+- (void)dismissDialogWithButtonTag:(id)buttonTag |
+ userInputStrings:(NSArray<NSString*>*)inputStrings; |
+ |
+@end |
+ |
+#endif // IOS_CLEAN_CHROME_BROWSER_UI_COMMANDS_DIALOG_COMMANDS_H_ |