Open Bug 1435864 Opened 6 years ago Updated 9 months ago

[META] Implement declarativeContent API

Categories

(WebExtensions :: General, enhancement, P5)

Product:
WebExtensions
Component:
General
Version:
59 Branch
Type:
enhancement

Tracking

(Not tracked)

Status:
ASSIGNED

People

(Reporter: mconca, Assigned: robwu)

References

(Depends on 3 open bugs)

Details

(Keywords: meta, Whiteboard: [declarative]) 

This is a tracking bug to add support for a delcarativeContent API.  The API should be backwards compatible with Chrome (https://developer.chrome.com/extensions/declarativeContent) but could also support additional actions.
Depends on: 1432647
Priority: -- → P3
Keywords: meta
Summary: Implement delcarativeContent API → [meta] Implement delcarativeContent API
Depends on: 1465994
Depends on: 1465995
Blocks: 1459029
Summary: [meta] Implement delcarativeContent API → [META] Implement delcarativeContent API
Product: Toolkit → WebExtensions
typo: delc -> decl
Summary: [META] Implement delcarativeContent API → [META] Implement declarativeContent API
Assignee: nobody → rob
Status: NEW → ASSIGNED
Iteration: --- → 63.5 - Sep 3
(Removing iteration; this is a metabug, so the work is tracked at the dependencies.)
Iteration: 63.5 - Sep 3 → ---
Whiteboard: [declarative]

This was scheduled for mid-nightly testing this month but has missed the deadline. It should likely slip to 67 at this point.

Depends on: 1315829

Soft freeze is coming up, and this feature cannot be completed before that. For QA, the target will be 68 instead of 67. This will be the last time that the target is moved.

Depends on: 1540215

I’m writing my first web extension for Chrome, because that's what my workplace uses. But I would love to add cross-browser support for Firefox. I’ll need declarativeContentAPI support to do so.

Please consider this message a vote in support of adding this feature!

The development of declarativeContent is currently on hold because the risk of the implementation does not balance against the potential benefits of it. For more details, see https://docs.google.com/document/d/1KjC2uAV0n5BszbyQjclzp2cLiOhWuKrTmqvqyz5ggKU/preview

There are several alternatives to the declarativeContent API, such as the tabs and webNavigation APIs, and using them results in code that is still compatible with Chrome.

Priority: P3 → P5
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.