manifest key to enable automatic injection of content scripts after installation/update #617
Labels
needs-triage: chrome
Chrome needs to assess this issue for the first time
supportive: firefox
Supportive from Firefox
supportive: safari
Supportive from Safari
Comments
|
Very much in favour of having this be aligned cross browsers! Safari also injects content scripts right after installation. As for the possible solutions. More in favour of 2-4. As 1; using an array for "run_at" would not be backwards compatible. Mixing the two also seems confusing rather than clarifying. |
|
This is also something I wrote some code for (https://github.com/fregante/webext-inject-on-install) but it requires the Related requests:
Here's what they could look like: {
"content_scripts": [{
"id": "main",
"matches": ["*://*.example.com/*"],
"scripts": ["content.js"],
"run_at": "document_idle",
+ "run_on_active_tab": true,
+ "run_on_extension_enabled": true
}]
}or {
"content_scripts": [{
"id": "main",
"matches": ["*://*.example.com/*"],
"scripts": ["content.js"],
"run_at": "document_idle",
+ "run_on": ["active_tab", "extension_enabled"]
}]
}or combine it with {
"content_scripts": [{
"id": "main",
"matches": ["*://*.example.com/*"],
"scripts": ["content.js"],
+ "run_at": ["document_idle", "active_tab", "extension_enabled"]
}]
} |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Benefits/goals:
matchesinhost_permissionsand doesn't supportexclude_matchesyet (#123).Possible solutions:
"run_at": ["document_start", "extension_installed", "extension_enabled"]i.e. an alternative array syntax forrun_at"run_at_extension": ["installed", "enabled"]i.e. an additional key"run_at_installed": trueand"run_at_enabled": true"run_at_installed_or_enabled": trueNotes:
"extension_invoked"in 1,"invoked"in 2,"run_at_invoked"in 3 and 4.content_scriptsshould copy the install note from MDN concepts.content_scripts.The text was updated successfully, but these errors were encountered: