This will require some toolkit support.
I'm not sure this is a P1 (it was filed as such a year ago), Bob did we have some tracking bugs for what needs to happen to allow this to work?
This is required for Chrome parity, but I agree that it may not be a P1. Native work is required to update nsIAlertsService to support the buttons. It doesn't look like a bug has been opened for that, so I created bug 1286536 and have marked it as blocking this bug. There are a few other things that we don't seem to support from chrome.notifications, such as notifications with multiple items, notifications which report progress, and the `requireInteraction` option . I'm not sure where we stand on implementing those or not. Kris, do you have any thoughts on those?  https://developer.chrome.com/extensions/notifications#type-NotificationOptions
Thanks for adding the blocking bug. Agree, its not a P1 so dropping.
I agree that it doesn't seem like a huge priority at the moment, given the amount of platform work required. Let's look at it again in the next quarter, or when bug 1225110 is fixed.
Any tentative date to fix this bug ? I'll plan my web extension accordingly.
(In reply to sankar88.aj from comment #6) > Any tentative date to fix this bug ? I'll plan my web extension accordingly. No, the code that generates notifications (independent of webextensions) doesn't yet have support for buttons, so that needs to happen before the corresponding webextensions apis get implemented. You can follow the dependent bug linked above, but it doesn't appear to be a high priority for anybody at the moment.