Closed
Bug 1776343
Opened 4 years ago
Closed 3 years ago
Allow multiple Firefox Messaging Systems providers to use RemoteL10n
Categories
(Firefox :: Messaging System, enhancement, P2)
Firefox
Messaging System
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: nalexander, Assigned: nalexander)
References
(Blocks 1 open bug)
Details
(Whiteboard: [fidedi-notifications])
Attachments
(1 obsolete file)
Right now, only the cfr provider can use the RemoteL10n module. This ticket tracks making that configurable, so that a new background task-specific provider can take advantage of this process.
| Assignee | ||
Comment 1•4 years ago
|
||
Updated•4 years ago
|
Iteration: --- → 104.1 - June 27 - July 8
Priority: -- → P1
| Assignee | ||
Updated•4 years ago
|
Whiteboard: [fidedi-notifications]
Updated•4 years ago
|
Updated•4 years ago
|
Attachment #9282736 -
Attachment description: Bug 1776343 - Allow multiple Firefox Messaging Systems providers to use RemoteL10n. r?pdahiya → WIP: Bug 1776343 - Allow multiple Firefox Messaging Systems providers to use RemoteL10n. r?pdahiya
Updated•4 years ago
|
Iteration: 104.1 - June 27 - July 8 → 104.2 - July 11 - July 22
Updated•4 years ago
|
Attachment #9282736 -
Attachment description: WIP: Bug 1776343 - Allow multiple Firefox Messaging Systems providers to use RemoteL10n. r?pdahiya → Bug 1776343 - Allow multiple Firefox Messaging Systems providers to use RemoteL10n. r?pdahiya
Updated•4 years ago
|
Attachment #9282736 -
Attachment is obsolete: true
Updated•3 years ago
|
Iteration: 104.2 - July 11 - July 22 → 105.1 - July 25 - Aug 5
Updated•3 years ago
|
Iteration: 105.1 - July 25 - Aug 5 → 105.2 - Aug 8 - Aug 19
Updated•3 years ago
|
Iteration: 106.1 - Aug 22 - Sept 2 → 106.2 - Sept 5 - Sept 16
Updated•3 years ago
|
Iteration: 106.2 - Sept 5 - Sept 16 → 107.1 - Sept 19 - Sept 30
Updated•3 years ago
|
Iteration: 107.1 - Sept 19 - Sept 30 → 107.2 - Oct 3 - Oct 14
Updated•3 years ago
|
Iteration: 107.2 - Oct 3 - Oct 14 → 108.1 - Oct 17 - Oct 28
Updated•3 years ago
|
Iteration: 108.1 - Oct 17 - Oct 28 → 108.2 - Oct 31 - Nov 11
Updated•3 years ago
|
Priority: P1 → P2
Updated•3 years ago
|
Iteration: 108.2 - Oct 31 - Nov 11 → 109.1 - Nov 14 - Nov 25
Updated•3 years ago
|
Iteration: 109.1 - Nov 14 - Nov 25 → 109.2 - Nov 28 - Dec 9
Updated•3 years ago
|
Iteration: 109.2 - Nov 28 - Dec 9 → 110.1 - Dec 12 - Dec 23
Updated•3 years ago
|
Iteration: 110.1 - Dec 12 - Dec 23 → 110.2 - Dec 26 - Jan 6
Updated•3 years ago
|
Iteration: 110.2 - Dec 26 - Jan 6 → 110.3 - Jan 9 - Jan 13
Updated•3 years ago
|
Iteration: 110.3 - Jan 9 - Jan 13 → 111.1 - Jan 16 - Jan 27
Updated•3 years ago
|
Iteration: 111.1 - Jan 16 - Jan 27 → 111.2 - Jan 30 - Feb 10
Updated•3 years ago
|
Iteration: 111.2 - Jan 30 - Feb 10 → 112.1 - Feb 13 - Feb 24
Updated•3 years ago
|
Iteration: 112.1 - Feb 13 - Feb 24 → 112.2 - Feb 27 - Mar 10
Updated•3 years ago
|
Iteration: 112.2 - Feb 27 - Mar 10 → ---
| Assignee | ||
Comment 2•3 years ago
|
||
For update notification experiments, we ended up only using the remote-experiments provider, which supports this already. If we wanted to land an in-product message provider (distinct from cfr, I guess) for background task messaging, then we'd need something like this. But right now, we don't need it -- so I'm closing.
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•