Open Bug 1612752 Opened 5 years ago Updated 3 years ago

Allow experimental APIs to be exposed to content contexts

Categories

(WebExtensions :: Experiments, enhancement, P5)

enhancement

Tracking

(Not tracked)

People

(Reporter: darktrojan, Unassigned)

Details

The docs say this:

Experimental APIs can (currently) only be exposed to extension pages, not to devtools pages or to content scripts.

The "currently" gives some hope that this might change, but I see no evidence of it. This would be particularly useful for Thunderbird where experiments are going to be heavily used for the next while.

content processes can just communicate with the background script to access the APIs, so I don't see us trying to focus on this. We'd probably consider taking a patch if someone wanted to work on it.

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