Chrome.scripting is undefined although added permissions for "scripting"

221 views
Skip to first unread message

Ben Bracha

unread,
Aug 21, 2023, 9:36:31 AM8/21/23
to chrome-debugging-protocol
I'm getting a strange error where chrome.scripting is undefined, although I added "scripting" to my manifest permissions.
I'm trying to use the chrome.scripting from my background script.

Any idea what am I missing?


"permissions"
: ["storage", "activeTab", "debugger", "scripting"],

usage:

chrome.scripting
.executeScript({
target : {tabId : customerTabId, allFrames : true},
func : invoke,
})

Ben Bracha

unread,
Aug 21, 2023, 9:37:49 AM8/21/23
to chrome-debugging-protocol
Oh, I see it is from minimum manifest version 3.
I was using 2.



--
You received this message because you are subscribed to the Google Groups "chrome-debugging-protocol" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chrome-debugging-p...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/chrome-debugging-protocol/5eb539af-db0f-4404-aeee-e5d426fb72a3n%40googlegroups.com.

Paul Irish

unread,
Aug 21, 2023, 3:01:22 PM8/21/23
to chrome-debugging-protocol
FWIW these are chrome extension API questions. The devtools protocol is distinct and unrelated to these APIs.

Stackoverflow is probably your best bet for support here.

Ben Bracha

unread,
Aug 22, 2023, 1:54:17 AM8/22/23
to Paul Irish, chrome-debugging-protocol
Reply all
Reply to author
Forward
0 new messages