Andre, there's a lot of UX questions posted to the folio link above. I was hoping you'd have the answer to these, given your involvement. If you could, please record your responses in this bug, not folio. Thanks! 

Just spoke with Jenn, we're going to consolidate the scale and resolution fields to just scale (as it is today). 

Mocks need to be updated to reflect this. We should the previous exploration on guidance for language: 
https://folio.googleplex.com/chrome-ux/mocks/280-chromeos-display-resolutions#%2Fchromeos-display-resolutions.png

Setting default priority/type

Setting default priority/type

Andre and I went through and responded. Alan/Steven can you let us know if anything else is needed?

I've consolidated scale and resolution into just scale, and in doing so, removed the advanced section.  Let me know what other issues there are. 

https://folio.googleplex.com/chrome-ux-specs-and-sources/Chrome%20Inner%20Pages/03-Settings/preview/cards#%2FPREVIEW_Displays.png%3Fz=width&c=show

Deleted: Screen Shot 2016-05-26 at 10.04.28 PM.png 100 KB

	Screen Shot 2016-05-26 at 10.04.28 PM.png 100 KB View Download

@stevenjb is anything more needed here?

Mocks need to be updated for:
* Display name instead of number
* Mirroring
* Overscan overlay needs a mock

Also we still need tracking issues for the new UI features (which will probably not make the MD Settings launch).

Issue 660601 has been merged into this issue.

We should polish this for 59. See also:

 issue 657951  Display settings: visual glitches

Working on the scale slider bar.

Re #9:
* Display name instead of number -- not sure what is meant by this? I see display names.
* Mirroring -- this works for me (see mirroring.png)
* Overscan overlay needs a mock -- dialog looks fine, except "OK" button should be "DONE" and should have blue background (see overscan.png)

A couple other issues to consider:
* Dragging the primary display shows a blue border on the edge of the extended display, but nothing happens the other way around. This didn't happen in the old Settings UI, was there a reason we added it? (see dragging.png)
* The monitor name is not required to have any padding around it (see "Internal display" in no-padding.png)

Deleted: overscan.png 46.4 KB

	overscan.png 46.4 KB View Download

Deleted: mirroring.png 5.5 KB

	mirroring.png 5.5 KB View Download

Deleted: dragging.png 186 KB

	dragging.png 186 KB View Download

Deleted: no-padding.png 8.0 KB

	no-padding.png 8.0 KB View Download

Hey, hope this is the right bug to chime in on.

I'm driving a 4K monitor, and the *current* behavior of the resolution slider gives me two settings that are both labeled "1920x1080". One is natively 1920x1080, and one renders 1920x1080 worth of stuff at high DPI and sends it to the monitor as 3840x2160.

Is this going to be fixed?

Most of the issues here are either fixed or WAI

Mine isn't -- you still can't tell the difference between 1920x1080 and 3840x2160 with 2x UI scaling. Should I file a separate bug?

The current display resolution setting is being revamped hidden away under advanced setting. It will instead be replaced with Display Size.
See https://bugs.chromium.org/p/chromium/issues/detail?id=790723

Oh, awesome, that looks great. Is that going to offer non-fuzzy UI scaling to all of those levels?

Non fuzzy UI scaling should already be available post M65.

You would need to enable the Display zoom setting flag under chrome://flags

This is absolutely fantastic from an accessibility perspective, thanks so much!