docs/chrome_settings.md - Issue 2719093002: Note Options deprecation in more places

Side by Side Diff: docs/chrome_settings.md

Issue 2719093002: Note Options deprecation in more places (Closed)

Patch Set: feedback Created 3 years, 9 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

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 **Any new features and bug fixes should be contributed to MD Settings, found in

	7 the /settings/ directories (as opposed to the /options/ directories).**

	8

	9 See: https://www.chromium.org/developers/updating-webui-for-material-design

	10

	11 Note: As the soft launch begins, chrome://settings may start surfacing the

	12 Material Design settings page. The deprecated "options" page will be available

	13 during this time at chrome://settings-frame, but will eventually be removed.

	14

	15 # Outdated

	16

	17 The remainder of this doc has not been substantially updated in some time, but

	18 is generally correct. Contact /options/ OWNERS if you have questions, but see

	19 the deprecation notice above.

	20

	21 ## What is chrome://settings?

	22

3 Chrome (version 10 and above) uses WebUI settings by default for all platforms.	23 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	24 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.	25 Windows and Chrome OS), or by typing chrome://settings into the address bar.

6	26

7 One advantage of chrome://settings over platform-native dialogs is that it is	27 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	28 shared by all platforms; therefore, it is easier to add new options UI and to

9 keep all platforms in sync.	29 keep all platforms in sync.

10	30

11 Note that at the time of this writing, DOMUI is being renamed to WebUI. The two	31 Note that at the time of this writing, DOMUI is being renamed to WebUI. The two

12 terms will be used interchangeably herein.	32 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	118 * 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	119 * 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	120 * the pref attribute matches that which is defined in

101 `chrome/common/pref_names.cc` and allows the prefs framework to	121 `chrome/common/pref_names.cc` and allows the prefs framework to

102 automatically keep it in sync with the value in C++	122 automatically keep it in sync with the value in C++

103 * the `i18n-content` value matches the string we defined in the WebUI handler.	123 * 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	124 The `textContent` of the `span` will automatically be set to the associated

105 text.	125 text.

106	126

107 In this example, no additional JS or CSS are needed.	127 In this example, no additional JS or CSS are needed.

OLD	NEW

« no previous file with comments | « chrome/browser/ui/webui/options/chromeos/OWNERS ('k') | no next file » | no next file with comments »