1851173 - scripting.getRegisteredScripts should only return scripts registered using the scripting API namespace

Status: RESOLVED FIXED

(WebExtensions :: General, defect, P2)

Description

[Luca Greco [:rpl] [:luca] [:lgreco]]

This is technically mainly a potential issue that only manifest_version 2 extensions can hit, because they have both contentScripts and scripting API namespaces available (while manifest_version 3 extensions can't hit it because the contentScripts API namespace isn't exposed to MV3 extensions at all).

If an extension uses both the contentScripts and scripting APIs, then contentScripts registered from the contentScripts.register API method are actually returned as part of the results of the scripting.getRegisteredContentScripts API method.

This behavior seems to be unintended and likely surprising and unexpected from an extension perspective.

This bugzilla issue tracks is tracking fixing the unexpected behavior.

Comment 1

[Luca Greco [:rpl] [:luca] [:lgreco]]

Attachment: Bug 1851173 - scripting.getRegisteredContentScripts shouldn't return content scripts registered through contentScripts.register. r?willdurand!

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/f896bcf490ca
scripting.getRegisteredContentScripts shouldn't return content scripts registered through contentScripts.register. r=willdurand

Comment 3

[Sandor Molnar[:smolnar]]

https://hg.mozilla.org/mozilla-central/rev/f896bcf490ca