Your code is not working because jQuery’s keydown() method does not actually trigger a “real” keydown event. Instead, jQuery looks up the “bound” event handlers in jQuery.cache, and calls the corresponding functions. Since your content script’s jQuery object differs from the page’s jQuery object, invoking .keydown() doesn’t cause any action. In your case, I suggest … Read more
You should always use OAuth 2.0 for authentication within extensions. Never pass the username/password because an attacker can simply steal such information. An example from Chromium regarding OAuth in extensions is Tutorial: OAuth. Additionally, there’s an experimental API available for OAuth 2.0, which is supposed to make the whole process a little easier. There’s a … Read more
Usually, you cannot create a Chrome extension which injects code in a devtools page. The “Discover DevTools Companion” extension from now on, referred to as DDC is allowed to do this, because this extension is whitelisted in the source code of Chromium: (this is no longer the case) // Whitelist “Discover DevTools Companion” extension from … Read more
There’s an issue for that on Google code: The solution is to pass analytics your own protocol check function or simply null for no checking, in an official way. This has to come after ga(‘create’, …) : ga(‘set’, ‘checkProtocolTask’, null); // Disable file protocol checking. So you don’t need to modify the original analytics.js script. … Read more
The matches key should specify where to expose these resources. You can use <all_urls> to expose them everywhere. “web_accessible_resources”: [{ “resources”: [“images/copy.svg”], “matches”: [“<all_urls>”], }],
To be precise, it’s the first 128 bits of the SHA256 of an RSA public key encoded in base 16. Another random bit of trivia is that the encoding uses a-p instead of 0-9a-f. The reason is that leading numeric characters in the host field of an origin can wind up being treated as potential … Read more
While I linked to this question that explains how to “pin” an ID for an unpacked extension, which would solve the practical problem OP faces, the question itself (as stated in the title) is interesting. If we look at the Chromium source, we will see that the ID is simply a SHA hash of a … Read more
For me it was sufficient to use @webcomponents/custom-elements package in my content.js. Also webcomponents-sd-ce.js weights about 80kb and custom-elements.min.js only 16kb. Just install it as a dependancy and import it in the content.js and let your package manager do the rest. npm i @webcomponents/custom-elements import ‘@webcomponents/custom-elements’ This is how I use it in my project … Read more
Site/URL permissions in ManifestV3 use a separate key: host_permissions “host_permissions”: [ “*://*.example.org/” ], “permissions”: [ “storage” ], More info in the official migration guide, make sure to study it.
The result of a script is the last expression being evaluated. So in your example you could use: chrome.tabs.executeScript( null, {code:”var x = 10; x”}, function(results){ console.log(results); } ); This will log [10] to the extension’s console. results is actually an array of values because if the page has more than one frame you can … Read more