Regression in ColorPicker ColorPalette

[Marv51]

Describe the bug

The GridView in ColorPicker that shows the ColorPalette, used to be two-way Binding to the selected color. The (much appreciated) work in #742 converted this to manual event subscription. Unfortunately, the path that updates the selected item when the color changes was forgotten. So effectively it is now a one-way binding from the control to the selected color.

Steps to reproduce

Add a ColorPicker to your project.

Go to the color palette tab.

Click on any color (let's say red)

Navigate to any other tab and change the selected color. (Maybe select blue in the color spectrum.)

Navigate back to the color palette tab.

Notice that the color chosen here previously (red) is still showing as selected. When you click on red, the selected color does not change back to red.

Expected behavior

I expect the ColorPalette to follow the selected color in the same way as the rest of the color choosing elements are.

Screenshots

repro-colorpicker.mp4

Code Platform

• UWP
• WinAppSDK / WinUI 3
• Web Assembly (WASM)
• Android
• iOS
• MacOS
• Linux / GTK

Windows Build Number

• Windows 10 1809 (Build 17763)
• Windows 10 1903 (Build 18362)
• Windows 10 1909 (Build 18363)
• Windows 10 2004 (Build 19041)
• Windows 10 20H2 (Build 19042)
• Windows 10 21H1 (Build 19043)
• Windows 10 21H2 (Build 19044)
• Windows 10 22H2 (Build 19045)
• Windows 11 21H2 (Build 22000)
• Other (specify)

Other Windows Build number

No response

App minimum and target SDK version

• Windows 10, version 1809 (Build 17763)
• Windows 10, version 1903 (Build 18362)
• Windows 10, version 1909 (Build 18363)
• Windows 10, version 2004 (Build 19041)
• Windows 10, version 2104 (Build 20348)
• Windows 11, version 22H2 (Build 22000)
• Other (specify)

Other SDK version

No response

Visual Studio Version

No response

Visual Studio Build Number

No response

Device form factor

No response

Additional context

No response

Help us help you

Yes, but only if others can assist.

[michael-hawker]

Thanks @Marv51 for this bug and the PR, we'll get this reviewed!

[AndrewKeepCoding]

Great catch @Marv51!