Open
Bug 1190681
Opened 9 years ago
Updated 1 year ago
Browser extension |notifications| API needs support for buttons in notifications
Categories
(WebExtensions :: Frontend, enhancement, P3)
Tracking
(Not tracked)
NEW
People
(Reporter: billm, Unassigned)
References
(Depends on 1 open bug, Blocks 1 open bug)
Details
(Keywords: dev-doc-needed, Whiteboard: [notifications]triaged)
This will require some toolkit support.
Reporter | ||
Updated•9 years ago
|
Priority: -- → P1
Reporter | ||
Updated•9 years ago
|
Component: Extension Compatibility → WebExtensions
Product: Firefox → Toolkit
Updated•9 years ago
|
Keywords: dev-doc-needed
Updated•9 years ago
|
Whiteboard: [notifications]
Updated•9 years ago
|
Flags: blocking-webextensions-
Updated•9 years ago
|
Whiteboard: [notifications] → [notifications]triaged
Updated•9 years ago
|
Updated•9 years ago
|
Comment 1•8 years ago
|
||
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?
Flags: needinfo?(bob.silverberg)
Comment 2•8 years ago
|
||
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 [1]. I'm not sure where we stand on implementing those or not. Kris, do you have any thoughts on those?
[1] https://developer.chrome.com/extensions/notifications#type-NotificationOptions
Updated•8 years ago
|
Flags: needinfo?(kmaglione+bmo)
Comment 3•8 years ago
|
||
Thanks for adding the blocking bug. Agree, its not a P1 so dropping.
Priority: P1 → P3
Comment 4•8 years ago
|
||
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.
Flags: needinfo?(kmaglione+bmo)
Updated•8 years ago
|
Component: WebExtensions: Untriaged → WebExtensions: Frontend
Flags: blocking-webextensions-
Comment 6•8 years ago
|
||
Any tentative date to fix this bug ? I'll plan my web extension accordingly.
Comment 7•8 years ago
|
||
(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.
Comment 8•7 years ago
|
||
Now that all legacy add-ons are disabled in the Firefox nightly, maybe this should have a higher priority.
Adblock Plus (WebExtensions) falls back to Window.confirm if notifications with buttons are not supported, but that won't work for WebExtensions either because bug #1203394. There is currently no fallback available.
Comment 9•7 years ago
|
||
> There is currently no fallback available.
https://developer.mozilla.org/en-US/Add-ons/WebExtensions/API/windows/create
Comment 10•7 years ago
|
||
Thanks, windows.create might work as a fallback. It's still not available on Android though.
Updated•7 years ago
|
Blocks: abp, webext-port-abp
Comment 11•7 years ago
|
||
With the release of Firefox Quantum my Gmail extension could definitely use a notification button to quickly delete incoming emails, just as it does with my the Chrome version of the extension.
Comment 12•7 years ago
|
||
Half a year later, still an issue. This doesn't seem to be blocked by anything.
Updated•6 years ago
|
Product: Toolkit → WebExtensions
Comment 13•5 years ago
|
||
(In reply to Kris Maglione [:kmag] from comment #4)
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.
I think there has been some activity in that bug, so hopefully a patch will come along here soon.
Updated•2 years ago
|
Severity: normal → S3
Comment hidden (advocacy) |
You need to log in
before you can comment on or make changes to this bug.
Description
•