It is evident that the callback to gets executed whenever it receives a message, with the first parameter being the message it receives. Since we want this script to be executed for Medium articles, we’ll use the declarative method for now.Īdd the following snippet to your manifest file: ) You can inject the script programmatically (from a background or popup file) or declaratively (execute the script automatically on a particular page).
The DOM is shared between all the content scripts and the original webpage’s JavaScript.įor our extension we also need access to the DOM to be able to modify the content of the webpage, so we need a content script. Just go to chrome://extensions and turn on developer mode from the top right-hand corner:Įach isolated world has its JavaScript environment that ensures libraries don’t conflict with each other.
If you're curious about the changes from version one to version two, you can find the changelog here.Īnd guess what? We already have enough to load our extension in the browser: We should use version two because version one was deprecated a long time ago. Last but not least, manifest_version specifies the manifest specification of our package targets.Whenever you want to release a new version of your extension, you'll need to update this field. The version key defines the current version of your extension (we are starting with 0.1).It has a slightly greater character limit of 132 characters. It’s also used both in extension management UI and the Chrome web store. Next is the description key, which is used to describe your extension.The name property is the primary identifier of the extension and will be used in the extension management UI and the Chrome web store.
0 kommentar(er)
