1435864 - [META] Implement declarativeContent API

Status: ASSIGNED

(WebExtensions :: General, enhancement, P5)

Description

[Mike Conca [:mconca]]

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.

Comment 1

[wOxxOm]

typo: delc -> decl

Comment 2

[Rob Wu [:robwu]]

(Removing iteration; this is a metabug, so the work is tracked at the dependencies.)

Comment 3

[Liz Henry (:lizzard) (relman/hg->git project)]

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

Comment 4

[Rob Wu [:robwu]]

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.

Comment 5

[Tony Rogers]

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!

Comment 6

[Rob Wu [:robwu]]

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.

Comment 7

[fregante]

I really wish declarative APIs were supported and more introduced. Declaring what I want to do is always going to be easier than doing it imperatively. Is calling a webNavigation API at every step of every HTTP request better?