OLD | NEW |
(Empty) | |
| 1 <h1 id="incognito">Manifest - Incognito</h1> |
| 2 |
| 3 <p> |
| 4 Either "spanning" or "split", to specify how this extension will |
| 5 behave if allowed to run in incognito mode. |
| 6 </p> |
| 7 |
| 8 <p> |
| 9 The default for extensions is "spanning", which means that the extension |
| 10 will run in a single shared process. Any events or messages from an incognito |
| 11 tab will be sent to the shared process, with an <em>incognito</em> flag |
| 12 indicating where it came from. Because incognito tabs cannot use this shared |
| 13 process, an extension using the "spanning" incognito mode will not be able to |
| 14 load pages from its extension package into the main frame of an incognito tab. |
| 15 </p> |
| 16 |
| 17 <p> |
| 18 The default for installable web apps is "split", |
| 19 which means that all app pages in |
| 20 an incognito window will run in their own incognito process. If the app or exten
sion contains a background page, that will also run in the incognito process. |
| 21 This incognito process runs along side the regular process, but has a separate |
| 22 memory-only cookie store. Each process sees events and messages only from its |
| 23 own context (for example, the incognito process will see only incognito tab upda
tes). |
| 24 The processes are unable to communicate with each other. |
| 25 </p> |
| 26 |
| 27 <p> |
| 28 As a rule of thumb, if your extension or app needs to load a tab in an incognito
browser, use |
| 29 <em>split</em> incognito behavior. If your extension or app needs to be logged |
| 30 into a remote server or persist settings locally, use <em>spanning</em> |
| 31 incognito behavior. |
| 32 </p> |
OLD | NEW |