Existing mocks for reference: https://folio.googleplex.com/chrome-ux-specs-and-sources/Chrome%20Inner%20Pages/03-Settings/preview/cards#%2FPREVIEW-About_ChromeOS.png%3Fz=half

My guess is that "Change channel" should be a dialog like it is today. It should follow the same general style as other dialogs, though I'm not sure if we have specs for (1) appearing/disappearing warning messages or (2) buttons that appear and change message.

It looks like we're missing a "Detailed build information" row. While we used to have a few properties bubble up to the top (version/platform/firmware) and a "More info..." link, I think it should be fine to add a "Build information" row below "Report an issue" in the mocks.

Yes, change channel should stay a dialog. 1.) the spec specifies proper spacing between mixed-content in a dialog (such as warning messages and radio buttons). You should be able to build something suitable, given the specs on spacing and typography. 2.) nothing changes in spec for button string text. 

dialogs
https://folio.googleplex.com/chrome-ux-specs-and-sources/Chrome%20Inner%20Pages/03-Settings/specs#%2FSPEC-settings_dialogs.png%3Fz=width

buttons
https://folio.googleplex.com/chrome-ux-specs-and-sources/Chrome%20Inner%20Pages/03-Settings/specs#%2FSPEC-settings_buttons.png%3Fz=width


Yes, detailed build is missing. I agree with Tom: it should be a row underneath report an issue. 

Thanks! 

Thanks for the clarifications so far. Here are two more questions.

1) Check for update: In the mocks both Chrome and ChromeOS show a "Check for update" button. But in the old Options this is possible only for ChromeOS. Chrome automatically checks for updates and applies them without a button. See attached screenshots.

2) "Open the help app" text. A help app exists only for ChromeOS. In Chrome the old Options simply open a website on a new tab. Should the text say "Open the help page" for Chrome?

Deleted: about_chromeos.png 189 KB

	about_chromeos.png 189 KB View Download

Deleted: about_chrome.png 32.7 KB

	about_chrome.png 32.7 KB View Download

Thanks for the screenshots

re: #1
Understood. That's just a mistake in the mocks 

re: #2
Let use "Get help with Chrome" and "Get help with ChromeOS" respectively 

@bettes: After implementing the "channel switcher" dialog, I am seeing a small UX issue I would like to run by you.

When the user changes release channels (ChromeOS only), there is no immediate feedback that the channel change has taken effect. Specifically the screens that the users sees are 
1->2->1->3 (see attachments).

After closing the channel switcher dialog, the user is still at the chrome://md-settings/help/details page, where the channel change is not reflected. User has to navigate one level-up to chrome://md-settings/help to see that the channel change has taken effect.

Should the "Channel" section on chrome://md-settings/help/details page be immediately updated to reflect that something is happening?

Deleted: about_ux_issue_1.png 55.7 KB

	about_ux_issue_1.png 55.7 KB View Download

Deleted: about_ux_issue_2.png 48.3 KB

	about_ux_issue_2.png 48.3 KB View Download

Deleted: about_ux_issue_3.png 57.0 KB

	about_ux_issue_3.png 57.0 KB View Download

Good catch! Some options:
1) Update the "Currently on beta" sub-title to something like "Updating to dev channel". Adding a spinner could be nice as well, but I'm not sure it's necessary.
2) Taking the user back to the top-level "About" page when the dialog is closed, so they can see the spinner and updating progress.

I agree #1 seems like the most straightforward approach, so I'm fine with that unless Alan feels differently.

#1 is definitely preferable, where the channel change is being reflected in the UI

@dpapad, can you fix this? Please re-assign to stevenjb@ if not.

There are a few issues I'm seeing on 56.0.2924.12 (Official Build) dev:
1) We don't show "Updating to [new channel]" after changing the channel
2) Opening the dialog again still shows the current channel, not the channel that was changed to.
3) The dialog size changes dramatically when a different channel is selected, in order to show the message. We should keep the width consistent, and make the dialog scroll if necessary.

1) Can we get a little more info than (1) in comment #7? Something better than "something like" :) 
2) Is now fixed:  issue 665705 
3) In progress:  issue 666878 

We can use this to continue to track (1).

dpapad@ - You can ahead and assign this to me if you aren't already working on it

For #1, let's go with "Currently on [channel]" for the normal UI, and when the user changes channel it goes to "Currently on [channel], updating to [channel]"