Implement receiving side of web notification inline replies

third_party/WebKit/Source/modules/notifications/NotificationAction.idl

Index: third_party/WebKit/Source/modules/notifications/NotificationAction.idl
diff --git a/third_party/WebKit/Source/modules/notifications/NotificationAction.idl b/third_party/WebKit/Source/modules/notifications/NotificationAction.idl
index be78856c3bc5028caa5b6d13f526f6d41ce61853..6dc56945a66773fa7a8a4de2210bae482535927d 100644
--- a/third_party/WebKit/Source/modules/notifications/NotificationAction.idl
+++ b/third_party/WebKit/Source/modules/notifications/NotificationAction.idl
@@ -4,8 +4,15 @@
 
 // https://notifications.spec.whatwg.org/#dictdef-notificationaction
 
+[RuntimeEnabled=NotificationInlineReplies] enum NotificationActionType {
+    "button",
+    "text"
+};
+
 dictionary NotificationAction {
     required DOMString action;
     required DOMString title;
     [RuntimeEnabled=NotificationActionIcons] USVString icon;
+    [RuntimeEnabled=NotificationInlineReplies] NotificationActionType type = "button";
+    [RuntimeEnabled=NotificationInlineReplies] DOMString? placeholder;

[Michael van Ouwerkerk, 2016/04/05 10:06:55]

How is null expressed in our implementation, what is the meaning of it? I would
expect that we show some kind of default placeholder string in that case,
instead of the empty string. It looks like we convert it to an empty string,
losing the distinction. It might as well not be nullable then, and have a
default value of "". And if it is nullable, can we assign a default value of
null here?

[Nina, 2016/04/05 13:28:22]

I modified the existing code to account for it.
Agreed, this will be reflected in the follow-up patch.
Keeping it nullable means we can distinguish between the case where the dev does
not want to specify a placeholder and when they want to specify a blank one.
Done!

 };