-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support inline replies #68
Comments
FYI: OS X and iOS also have this so compatibility with their APIs should also be taken into account. |
I'm still looking into this, but one thing comes to mind. As actions are only supported on persistent notifications, the nullable text reply could be more narrowly scoped by setting it on the event for onnotificationclick instead of the notification object. |
I'm probably missing something obvious. If a notification has been created, there's already a browser window somewhere with the page open. Do you want a way for the page to say "call this js function with the string entered in the quick reply field"? |
@hober This is for persistent notifications, which are generated from service workers, and those may run in the background without any browser window being open. |
Ahh. That's not how notifications work on OS X, so I'm not sure what kind of input I can provide here then. |
PR in progress at #132 |
What is the status on this? I've looked at the PR which hasn't gotten updated since last year but surprisingly found this chromium issue to be already closed and marked as fixed. Can I already be using inline replies but they will only work in chrome? If yes, where can I read more about the API? |
Android N and Windows 10 support showing a text input in a notification. This feature would allow users to quickly write a reply without launching a new browser window. The benefits are more evident in low resource devices, where the cost of doing so is non trivial.
I suggest adding a
boolean requestReply
attribute toNotificationAction
. If it's true, the user agent should provide a way to let the user activate the action with a text response. Naturally, this means a new attributeDOMString reply
is added toNotification
, conveying the reply text (which may be empty) or null if no reply was requested.What do you think?
The text was updated successfully, but these errors were encountered: