Chromium Code Reviews Chromium Code Reviews
Issue 2719093002:
Note Options deprecation in more places (Closed)
| OLD | NEW |
|---|---|
| 1 # What is chrome://settings? | 1 # Deprecation |
| 2 | 2 |
| 3 This doc refers to "options", the soon-to-be-deprecated version of | |
| 4 chrome://settings being replaced by Material Design Settings. | |
| 5 | |
| 6 We encourage any new features and bug fixes to be contributed to MD Settings, | |
| 7 which can be found in the /settings/ directories (as opposed to the /options/ | |
| 8 directories). | |
| 9 | |
| 10 We won't block high-priority updates to Options, especially for bug fixes or | |
| 11 urgent features, but know that your team will also responsible for implementing | |
| 12 those new features in MD Settings. | |
|
Dan Beam
2017/02/27 18:48:15
can you just remove this paragraph? i don't want
michaelpg
2017/02/27 18:58:29
Done.
| |
| 13 | |
| 14 See: https://www.chromium.org/developers/updating-webui-for-material-design | |
| 15 | |
| 16 Note: As the soft launch begins, chrome://settings may start surfacing the | |
| 17 Material Design settings page. The deprecated "options" page will be available | |
| 18 during this time at chrome://settings-frame, but will eventually be removed. | |
| 19 | |
| 20 # Outdated | |
| 21 | |
| 22 The remainder of this doc has not been substantially updated in some time, but | |
| 23 is generally correct. Contact /options/ OWNERS if you have questions, but see | |
| 24 the deprecation notice above. | |
| 25 | |
| 26 ## What is chrome://settings? | |
| 27 | |
| 3 Chrome (version 10 and above) uses WebUI settings by default for all platforms. | 28 Chrome (version 10 and above) uses WebUI settings by default for all platforms. |
| 4 Access it via the wrench menu ("Preferences" on Mac and Linux; "Options" on | 29 Access it via the wrench menu ("Preferences" on Mac and Linux; "Options" on |
| 5 Windows and Chrome OS), or by typing chrome://settings into the address bar. | 30 Windows and Chrome OS), or by typing chrome://settings into the address bar. |
| 6 | 31 |
| 7 One advantage of chrome://settings over platform-native dialogs is that it is | 32 One advantage of chrome://settings over platform-native dialogs is that it is |
| 8 shared by all platforms; therefore, it is easier to add new options UI and to | 33 shared by all platforms; therefore, it is easier to add new options UI and to |
| 9 keep all platforms in sync. | 34 keep all platforms in sync. |
| 10 | 35 |
| 11 Note that at the time of this writing, DOMUI is being renamed to WebUI. The two | 36 Note that at the time of this writing, DOMUI is being renamed to WebUI. The two |
| 12 terms will be used interchangeably herein. | 37 terms will be used interchangeably herein. |
| (...skipping 85 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... | |
| 98 * the `checkbox` class allows us to style all checkboxes the same via CSS | 123 * the `checkbox` class allows us to style all checkboxes the same via CSS |
| 99 * the class and ID are in dash-form * the i18n-content value is in camelCase | 124 * the class and ID are in dash-form * the i18n-content value is in camelCase |
| 100 * the pref attribute matches that which is defined in | 125 * the pref attribute matches that which is defined in |
| 101 `chrome/common/pref_names.cc` and allows the prefs framework to | 126 `chrome/common/pref_names.cc` and allows the prefs framework to |
| 102 automatically keep it in sync with the value in C++ | 127 automatically keep it in sync with the value in C++ |
| 103 * the `i18n-content` value matches the string we defined in the WebUI handler. | 128 * the `i18n-content` value matches the string we defined in the WebUI handler. |
| 104 The `textContent` of the `span` will automatically be set to the associated | 129 The `textContent` of the `span` will automatically be set to the associated |
| 105 text. | 130 text. |
| 106 | 131 |
| 107 In this example, no additional JS or CSS are needed. | 132 In this example, no additional JS or CSS are needed. |
| OLD | NEW |
