[MacViews] Bring button stroke and shadow up to spec. |
||||
Issue descriptionI am creating specs for each button state, and will add them as separate notes instead of all at once. The four states are Normal, Focused, Pressed, and Disabled. Note that the Primary button will have its own, separate bug. ========= Button, Normal State top edge: (0xCC, 0xCC, 0xCC, 0xFF) side edges: (0xBA, 0xBA, 0xBA, 0xFF) bottom edge: (0x9D, 0x9D, 0x9D, 0xFF) shadow: (0x00, 0x00, 0x00, 0x1C) Screenshot attached as reference.
,
Apr 14 2016
Button, Pressed State Interior: (0xFA, 0xFA, 0xFA, 0xFF) top edge: (0xCC, 0xCC, 0xCC, 0xFF) side edge: (0xBA, 0xBA, 0xBA, 0xFF) bottom edge: (0x9D, 0x9D, 0x9D, 0xFF) 1pt shadow: (0x00, 0x00, 0x00, 0x1C) 2nd 1pt Shadow: (0x00, 0x00, 0x00, 0x05)
,
Apr 14 2016
Button, Disabled state Text @ 50% opacity Interior: (0xF6, 0xF6, 0xF6, 0xFF) top edge: (0xD2, 0xD2, 0xD2, 0xFF) side edge: (0xCA, 0xCA, 0xCA, 0xFF) bottom edge: (0xBE, 0xBE, 0xBE, 0xFF) 1pt shadow: (0x00, 0x00, 0x00, 0x0D) 2nd 1pt Shadow: (0x00, 0x00, 0x00, 0x03)
,
Apr 14 2016
(Redo of normal state, to include spec for second line of shadow) Button, Normal State Interior: (0xFF, 0xFF, 0xFF, 0xFF) top edge: (0xCC, 0xCC, 0xCC, 0xFF) side edges: (0xBA, 0xBA, 0xBA, 0xFF) bottom edge: (0x9D, 0x9D, 0x9D, 0xFF) 1pt shadow: (0x00, 0x00, 0x00, 0x1C) 2nd 1pt Shadow: (0x00, 0x00, 0x00, 0x05)
,
Apr 14 2016
For the button focused state, let's go with following for now:
Focus ring color: (0x79, 0xA7, 0xE9, 0x94)
Focus ring width: 3pt, overlapping the button edge by 1pt
Re: the radius of the focus ring, how does Skia do its drawing? Do you need to define a path whose center lay along the centerline of the focus ring, and then change the line width to 3pt so that you an extra pixel on either side? Or does starting with the button's path and changing the line width cause the stroke to get fatter on the outside?
,
Apr 15 2016
One more thing: button text color should be (0x21, 0x21, 0x21, 0xFF), and (0x21, 0x21, 0x21, 0x7F) when disabled.
,
Apr 15 2016
,
Apr 15 2016
I'm going to add this to Issue 543686 , which is the existing tracking bug.
,
Apr 20 2016
|
||||
►
Sign in to add a comment |
||||
Comment 1 by shrike@chromium.org
, Apr 14 2016