Closed Bug 1498343 Opened 6 years ago Closed 6 years ago

Make it easier to recognize an extension that have access to the userScript.setScriptAPIs API method

Categories

(WebExtensions :: General, defect, P1)

defect

Tracking

(firefox64 fixed)

RESOLVED FIXED
mozilla64
Tracking Status
firefox64 --- fixed

People

(Reporter: rpl, Assigned: rpl)

References

Details

Attachments

(3 files)

This issue goal is to make it easier to recognize an extension that have access to the userScripts.setScriptAPIs API method based on its manifest.json file.
Assignee: nobody → lgreco
Status: NEW → ASSIGNED
Blocks: 1437098
Priority: -- → P1
Pushed by luca.greco@alcacoop.it: https://hg.mozilla.org/integration/autoland/rev/c68fc2d03471 Fix and re-enable userScript test disabled in Bug 1498343. r=zombie https://hg.mozilla.org/integration/autoland/rev/a0aa0b0aa078 Add more assertions related to behaviors on redefined globals and prototype methods in the userScript tests. r=mixedpuppy https://hg.mozilla.org/integration/autoland/rev/681ffcabae79 Make it easier to recognize an extension that have access to the userScript.setScriptAPIs API method. r=mixedpuppy
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla64
Marking as qe-verify-, as most of the changes are actually test-only and the only part of it that isn't test-only it is already tested in automated test (as part of the same commit that applied the change).
Flags: qe-verify-
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: