Note: There are a few cases of duplicates in user autocompletion which are being worked on.

Browser extension |notifications| API needs support for buttons in notifications

NEW
Unassigned

Status

()

Toolkit
WebExtensions: Frontend
P3
normal
2 years ago
3 months ago

People

(Reporter: billm, Unassigned)

Tracking

(Depends on: 1 bug, Blocks: 1 bug, {dev-doc-needed})

34 Branch
dev-doc-needed
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [notifications]triaged)

(Reporter)

Description

2 years ago
This will require some toolkit support.
(Reporter)

Updated

2 years ago
Priority: -- → P1
(Reporter)

Updated

2 years ago
Component: Extension Compatibility → WebExtensions
Product: Firefox → Toolkit
Keywords: dev-doc-needed

Updated

2 years ago
Whiteboard: [notifications]

Updated

2 years ago
Depends on: 1213455

Updated

2 years ago
Flags: blocking-webextensions-

Updated

2 years ago
Whiteboard: [notifications] → [notifications]triaged
Blocks: 1213455
No longer depends on: 1213455
Blocks: 1256627
No longer blocks: 1256627
See Also: → bug 1274559
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)
Depends on: 1286536
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
Depends on: 1225110
Flags: needinfo?(bob.silverberg)
Flags: needinfo?(kmaglione+bmo)
Thanks for adding the blocking bug. Agree, its not a P1 so dropping.
Priority: P1 → P3
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

10 months ago
Component: WebExtensions: Untriaged → WebExtensions: Frontend
Flags: blocking-webextensions-

Updated

4 months ago
Duplicate of this bug: 1348726

Comment 6

4 months ago
Any tentative date to fix this bug ? I'll plan my web extension accordingly.

Comment 7

4 months 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.
You need to log in before you can comment on or make changes to this bug.