Chromium Code Reviews| OLD | NEW |
|---|---|
| (Empty) | |
| 1 <div id="pageData-name" class="pageData">Preferences</div> | |
| 2 | |
| 3 <!-- BEGIN AUTHORED CONTENT --> | |
| 4 <p id="classSummary"> | |
| 5 The <code>chrome.preferences</code> module contains a prototype for giving other | |
| 6 modules access to manage Chrome's preferences. This prototype is used for | |
|
kathyw
2011/05/24 18:57:50
Chrome's preferences
-> Chrome-related preference
battre
2011/05/24 19:18:03
Done.
| |
| 7 example for <a | |
| 8 href="proxy.html#property-settings"><code>chrome.proxy.settings</code></a>. | |
| 9 </p> | |
| 10 | |
| 11 <h2 id="description">Functions</h2> | |
|
kathyw
2011/05/24 18:57:50
Functions -> Overview
(otherwise, this sounds lik
battre
2011/05/24 19:18:03
Done.
| |
| 12 | |
| 13 <p> | |
| 14 The preferences API provides a commen set of functions | |
|
kathyw
2011/05/24 18:57:50
commen -> common
battre
2011/05/24 19:18:03
Done.
| |
| 15 (<code>getEffective()</code>, <code>set()</code>, and <code>clear()</code>) as | |
| 16 well as an event publisher (<code>onChangeEffective</code>) for various | |
| 17 preferences in Chrome. The <a href="proxy.html#overview-examples">proxy settings | |
| 18 examples</a> demonstrate how these functions are intended to be used. | |
| 19 </p> | |
| 20 | |
| 21 <h2 id="lifecycle">Life cycle of preferences</h2> | |
|
kathyw
2011/05/24 18:57:50
Delete this heading? Until there's an incognito st
battre
2011/05/24 19:18:03
Done.
| |
| 22 | |
| 23 <p> | |
| 24 The life cycle of preferences depends on whether they are set for regular or | |
| 25 incognito profiles. Currently, preferences can only be set for regular profiles. | |
|
kathyw
2011/05/24 18:57:50
It seems weird to talk about incognito life cycles
battre
2011/05/24 19:18:03
Done.
| |
| 26 </p> | |
| 27 | |
| 28 <p> | |
| 29 Preferences for <em>regular profiles</em> are persisted to disk. Once set, they | |
|
kathyw
2011/05/24 18:57:50
"persisted to disk" sounds a little old fashioned
battre
2011/05/24 19:18:03
Done. I'd like to change it back to "Preferences f
| |
| 30 remain in place until they are cleared by the governing extension, or the | |
| 31 governing extension is disabled or uninstalled. | |
| 32 </p> | |
| 33 | |
| 34 <h2 id="precedence">Precedence</h2> | |
| 35 | |
| 36 <p> | |
| 37 Chrome manages preferences on different layers. The following list describes the | |
| 38 layers that may influence the effective preferences, in increasing order of | |
| 39 precedence. | |
| 40 <ol> | |
| 41 <li>System preferences provided by the operating system</li> | |
| 42 <li>Command line parameters</li> | |
|
kathyw
2011/05/24 18:57:50
-> Command-line options
(to be consistent with ph
battre
2011/05/24 19:18:03
Done.
| |
| 43 <li>Preferences set by extensions</li> | |
| 44 <li>Policies</li> | |
| 45 </ol> | |
| 46 </p> | |
| 47 | |
| 48 <p> | |
| 49 As the list implies, policies might overrule any changes that you specify with | |
| 50 your extension. | |
| 51 </p> | |
| 52 | |
| 53 <!-- | |
| 54 <p> | |
| 55 As discussed above, Chrome allows using different preferences for regular | |
| 56 windows and incognito windows. The following example illustrates the behavior. | |
| 57 Assume that no policy overrides the preferences and that an extension can set | |
| 58 preferences for regular windows <b>(R)</b> and preferences for incognito windows | |
| 59 <b>(I)</b>. | |
| 60 </p> | |
| 61 | |
| 62 <p> | |
| 63 <ul> | |
| 64 <li>If only <b>(R)</b> is set, these preferences are effective for both | |
| 65 regular and incognito windows.</li> | |
| 66 <li>If only <b>(I)</b> is set, these preferences are effective for only | |
| 67 incognito windows. Regular windows use the preferences determined by the lower | |
| 68 layers (command-line options and system settings).</li> | |
| 69 <li>If both <b>(R)</b> and <b>(I)</b> are set, the respective preferences are | |
| 70 used for regular and incognito windows.</li> | |
| 71 </ul> | |
| 72 </p> | |
| 73 --> | |
| 74 | |
| 75 <p> | |
| 76 If two extensions want to set the same preference to different values, the | |
| 77 extension installed last takes precedence over the other extensions. | |
|
kathyw
2011/05/24 18:57:50
extension installed last
-> most recently install
kathyw
2011/05/24 18:57:50
"two" -> "two or more"
(so that "other extensions
battre
2011/05/24 19:18:03
Done.
battre
2011/05/24 19:18:03
Done.
| |
| 78 <!-- If the | |
| 79 extension installed last sets only <b>(I)</b>, the preference of regular windows | |
| 80 can be defined by previously installed extensions. --> | |
| 81 </p> | |
| 82 | |
| 83 <p> | |
| 84 The <em>effective</em> preference value is the setting that results from | |
| 85 considering the preference rules. It is used by Chrome. | |
| 86 <p> | |
| 87 | |
| 88 <!-- END AUTHORED CONTENT --> | |
| OLD | NEW |