f943db7ad5
* Execute content script in isolated world * Inject script into newly created extension worlds * Create new content_script_bundle for extension scripts * Initialize chrome API in content script bundle * Define Chrome extension isolated world ID range 1 << 20 was chosen as it provides a sufficiently large range of IDs for extensions, but also provides a large enough buffer for any user worlds in [1000, 1 << 20). Ultimately this range can be changed if any user application raises it as an issue. * Insert content script CSS into document This now avoids a script wrapper to inject the style sheet. This closely matches the code used by chromium in `ScriptInjection::InjectCss`. * Pass extension ID to isolated world via v8 private |
||
---|---|---|
.. | ||
api | ||
printing | ||
resources/mac | ||
atom_autofill_agent.cc | ||
atom_autofill_agent.h | ||
atom_render_frame_observer.cc | ||
atom_render_frame_observer.h | ||
atom_render_view_observer.cc | ||
atom_render_view_observer.h | ||
atom_renderer_client.cc | ||
atom_renderer_client.h | ||
atom_sandboxed_renderer_client.cc | ||
atom_sandboxed_renderer_client.h | ||
content_settings_observer.cc | ||
content_settings_observer.h | ||
guest_view_container.cc | ||
guest_view_container.h | ||
preferences_manager.cc | ||
preferences_manager.h | ||
renderer_client_base.cc | ||
renderer_client_base.h | ||
web_worker_observer.cc | ||
web_worker_observer.h |