Rewrite with declarative APIs #9
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #4
The previous versions of
webext-dynamic-content-scriptstried to do something that was not possible while only truly supporting its main use:automatically registering existing scripts on new domains.
Migration from v5
DCS.addToTab
Use
chrome.tabs.executeScript/chrome.tabs.insertCSSdirectly. Also see my next comment.If you want to ensure scripts are only injected once, try webext-content-script-ping.
DCS.addToFutureTabs
With argument: DCS.addToFutureTabs(scripts)
Use Firefox’ new contentScripts.register API; there's a polyfill for Chrome.
Without argument: DCS.addToFutureTabs()
You can keep using
webext-dynamic-content-scriptsbut:Or if you don't use a bundler, you only need include it as a background script:
{ "background": { "scripts": [ "webext-dynamic-content-scripts.js" ] } }