electron/spec/fixtures/extensions/content-script-document-start/manifest.json

{
    "name": "document-start",
    "version": "1.0",
    "description": "",
    "content_scripts": [
      {
        "matches": ["<all_urls>"],
        "js": ["start.js"],
        "run_at": "document_start"
      }
    ],
    "manifest_version": 2
}
feat: support chrome extensions in sandboxed renderer (#16218) * Add content script injector to sandboxed renderer * Fix 'getRenderProcessPreferences' binding to the wrong object * Pass getRenderProcessPreferences to content-scripts-injector * Emit document-start and document-end events in sandboxed renderer * Use GetContext from RendererClientBase * Prevent script context crash caused by lazily initialization * Remove frame filtering logic for onExit callback Since we're keeping track of which frames we've injected the bundle into, this logic is redundant. * Add initial content script tests * Add contextIsolation variants to content script tests * Add set include * Fix already loaded extension error * Add tests for content scripts 'run_at' options * Catch script injection eval error when CSP forbids it This can occur in a rendered sandbox when a CSP is enabled. We'll need to switch to using isolated worlds to fix this. * Fix content script tests not properly cleaning up extensions * Fix lint and type errors 2019-03-08 00:00:28 +00:00			`{`
			`"name": "document-start",`
			`"version": "1.0",`
			`"description": "",`
			`"content_scripts": [`
			`{`
			`"matches": ["<all_urls>"],`
			`"js": ["start.js"],`
			`"run_at": "document_start"`
			`}`
			`],`
			`"manifest_version": 2`
chore: strip trailing whitespace (#35969) 2023-02-01 11:59:16 +00:00			`}`