OLD | NEW |
---|---|
1 <p id="bg"> | 1 <p id="bg"> |
2 Makes Chrome start up early and and shut down late, so that apps and extensions can have a longer life. | 2 Makes Chrome start up early and and shut down late, so that apps and extensions can have a longer life. |
3 </p> | 3 </p> |
4 | 4 |
5 <p> | 5 <p> |
6 When any installed hosted app, packaged app, or extension has "background" permi ssion, Chrome runs (invisibly) as soon as the user logs into their computer&mdas h;before the user launches Chrome. The "background" permission also makes Chrome continue running (even after its last window is closed) until the user explicit ly quits Chrome. | 6 When any installed hosted app, packaged app, or extension has "background" permi ssion, Chrome runs (invisibly) as soon as the user logs into their computer&mdas h;before the user launches Chrome. The "background" permission also makes Chrome continue running (even after its last window is closed) until the user explicit ly quits Chrome. |
7 </p> | 7 </p> |
8 | 8 |
9 <p class="note"> | 9 <p class="note"> |
10 <b>Note:</b> Disabled apps and extensions are treated as if they aren't instal led. | 10 <b>Note:</b> Disabled apps and extensions are treated as if they aren't instal led. |
11 </p> | 11 </p> |
12 | 12 |
13 <p> | 13 <p> |
14 You typically use the "background" permission with a <a href="background_pages.h tml">background page</a>, <a href="event_pages.html">event page</a> or (for host ed apps) a <a href="http://code.google.com/chrome/apps/docs/background.html">bac kground window</a>. | 14 You typically use the "background" permission with a <a href="background_pages"> background page</a>, <a href="event_pages">event page</a> or (for hosted apps) a <a href="http://code.google.com/chrome/apps/docs/background.html">background wi ndow</a>. |
mkearney1
2014/05/14 19:56:06
I'm guessing http://code.google.com/chrome/apps/do
ahernandez
2014/05/14 20:13:45
That link works for me
| |
15 </p> | 15 </p> |
OLD | NEW |