Closed Bug 1594232 Opened 5 years ago Closed 4 years ago

support content_security_policy.isolated_world in manifest

Categories

(WebExtensions :: General, task, P2)

Product:
WebExtensions
Component:
General
Type:
task

Tracking

(firefox74 fixed)

Status:
RESOLVED FIXED
Milestone:
mozilla74
Tracking Flags:
Tracking Status
firefox74 --- fixed

People

(Reporter: mixedpuppy, Assigned: mixedpuppy)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

Bug 1594232 support isolated_world alias in extension manifest
47 bytes, text/x-phabricator-request
Details | Review

Older information led to using content_security_policy.content_scripts, but Chrome claims they will use content_security_policy.isolated_world. IMO content_scripts is better, but lets aim for compatibility.

Assignee: nobody → mixedpuppy
Status: NEW → ASSIGNED
Pushed by scaraveo@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/22135e7e3143
support isolated_world alias in extension manifest r=robwu

https://hg.mozilla.org/mozilla-central/rev/22135e7e3143

Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox74: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla74

Hello,

Will this require manual validation? If yes, please provide some steps to reproduce in order to correctly test it and also, please set the "qe-verify+" flag. Otherwise, could the "qe-verify-" flag be added?

Thanks!

Flags: needinfo?(mixedpuppy)
Flags: needinfo?(mixedpuppy) → qe-verify-

isolated_world never shipped in Chrome - https://bugzilla.mozilla.org/show_bug.cgi?id=1581611#c10

I'm going to remove it from the BCD.

See Also: → 1581611
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: