Microsoft-ui-xaml: Update SplitButton

[sravya03]

Summary

Update the SplitButton to a new visual design, separating the button and drop down.

Rationale

1) Visually separate the two hit targets since they currently blend together and unintentionally look like one hit target
2) Is not visually distinct from the dropdown control (i.e. a split button and a drop down can appear to look like the same control)

[mdtauk]

I think you mean the Split Button, as the Drop Down Button is a single touch target...

[chigy]

I think you mean the Split Button, as the Drop Down Button is a single touch target...

@mdtaulk , yup, SplitButton. Thanks for the correction. I've corrected the item.

[Poopooracoocoo]

Is this related to #899?

[chigy]

Is this related to #899?

@Poopooracoocoo , no it is not.

[mdtauk]

@chigy not directly, but it is about making the two separate touch targets within the SplitButton control more obvious visually - which is what the discussion in issue #899 is considering

[chigy]

@chigy not directly, but it is about making the two separate touch targets within the SplitButton control more obvious visually - which is what the discussion in issue #899 is considering

Similar but not exactly the same. #899 is about changing the system style of what we call buddy button that lives inside the TextBox OR proposing not to use buddy button and use multiple buttons. This request is literally making two buttons separated visually.

[chigy]

Status update:

Visual comp is added.

[mdtauk]

I have updated my design following the proposed 4 button styles

[mdtauk]

Here is a more thorough design idea for the Split Button - including the toggled states.

[msft-github-bot]

:tada:This issue was addressed in #1173, which has now been successfully released as Microsoft.UI.Xaml v2.2.190830001.:tada:

Handy links:

• Release Notes
• Official Nuget Release