summaryrefslogtreecommitdiffstats
path: root/chrome/common/extensions/docs/background_pages.html
diff options
context:
space:
mode:
Diffstat (limited to 'chrome/common/extensions/docs/background_pages.html')
-rwxr-xr-xchrome/common/extensions/docs/background_pages.html14
1 files changed, 13 insertions, 1 deletions
diff --git a/chrome/common/extensions/docs/background_pages.html b/chrome/common/extensions/docs/background_pages.html
index 84101a3..e47f59c 100755
--- a/chrome/common/extensions/docs/background_pages.html
+++ b/chrome/common/extensions/docs/background_pages.html
@@ -224,7 +224,19 @@ The background page is similar to a toolstrip,
in that it is an HTML page that runs in the extension process.
The difference is that the background page exists
for the lifetime of your extension,
-and only one instance of it at a time is active.</p>
+and only one instance of it at a time is active.
+</p>
+
+<p>
+In a typical extension with a background page,
+the UI —
+toolstrips, page actions, and so on —
+is implemented with dumb views.
+When the view needs some state,
+it requests the state from the background page.
+When the background page notices a state change,
+the background page tells the views to update.
+</p>
<h2 id="manifest">Manifest</h2>