# Content Scripts #
Almost all interesting add-ons will need to interact with web content or the
browser's user interface. For example, they may need to access and modify the
content of web pages or be notified when the user clicks a link.
The SDK provides several core modules to support this:
**[context-menu](modules/sdk/context-menu.html)**
Add items to the browser's context menu.
**[panel](modules/sdk/panel.html)**
Create a dialog that can host web content.
**[page-worker](modules/sdk/page-worker.html)**
Retrieve a page and access its content, without displaying it to the user.
**[page-mod](modules/sdk/page-mod.html)**
Execute scripts in the context of selected web pages.
**[tabs](modules/sdk/tabs.html)**
Manipulate the browser's tabs, including the web content displayed in the tab.
**[widget](modules/sdk/widget.html)**
Host an add-on's user interface, including web content.
Firefox is moving towards a model in which it uses separate
processes to display the UI, handle web content, and execute add-ons. The main
add-on code will run in the add-on process and will not have direct access to
any web content.
This means that an add-on which needs to interact with web content needs to be
structured in two parts:
* the main script runs in the add-on process
* any code that needs to interact with web content is loaded into the web
content process as a separate script. These separate scripts are called
_content scripts_.
A single add-on may use multiple content scripts, and content scripts loaded
into the same context can interact directly with each other as well as with
the web content itself. See the chapter on
communicating with other scripts.
The add-on script and content script can't directly access each other's state.
Instead, you can define your own events which each side can emit, and the
other side can register listeners to handle them. The interfaces are similar
to the event-handling interfaces described in the
[Working with Events](dev-guide/guides/events.html) guide.
The diagram below shows an overview of the main components and their
relationships. The gray fill represents code written by the add-on developer.
This might sound complicated but it doesn't need to be. The following add-on
uses the [page-mod](modules/sdk/page-mod.html) module to replace the
content of any web page in the `.co.uk` domain by executing a content script
in the context of that page:
var pageMod = require("sdk/page-mod");
pageMod.PageMod({
include: ["*.co.uk"],
contentScript: 'document.body.innerHTML = ' +
'"this page has been eaten
";'
});
In this example the content script is supplied directly to the page mod via
the `contentScript` option in its constructor, and does not need to be
maintained as a separate file at all.
The next few chapters explain content scripts in detail:
* [Loading Content Scripts](dev-guide/guides/content-scripts/loading.html):
how to attach content scripts to web pages, and how to control the point at
which they are executed
* [Accessing the DOM](dev-guide/guides/content-scripts/accessing-the-dom.html):
detail about the access content scripts get to the DOM
* [Communicating With Other Scripts](dev-guide/guides/content-scripts/communicating-with-other-scripts.html):
detail about how content scripts can communicate with "main.js", with other
content scripts, and with scripts loaded by the web page itself
* [Communicating Using port](dev-guide/guides/content-scripts/using-port.html):
how to communicate between your add-on and its content scripts using the
port object
* [Communicating using postMessage()](dev-guide/guides/content-scripts/using-postmessage.html):
how to communicate between your add-on and its content scripts using the
postMessage() API
* [Example](dev-guide/guides/content-scripts/reddit-example.html):
a simple example add-on using content scripts