11.3.0-rc1 Released

[MrJul]

Full Changelog: 11.3.0-beta2...11.3.0-rc1

What's Changed

This list contains only changes made since 11.3.0-beta2.

Enhancements

• Pick nearest parent if container query doesn't specify container name by @emmauss in Pick nearest parent if container query doesn't specify container name #18707
• Add XML doc comments to RegisterDirect warning about unsetValue by @AnastassiaP in Add XML doc comments to RegisterDirect warning about unsetValue and d… #18719
• Added small banner about Accelerate by @MikeCodesDotNET in Added small banner about accelerate. #18723

Fixes

Only in 11.3.0-rc1:

• Fix height queries not matching when container name is set, remove unused query grammer and allow nesting selector in container styles by @emmauss in Fix height queries not matching when container name is set, remove unused query grammer and allow nesting selector in container styles #18659

Ported from 11.2.8:

• Keep SelectingItemsControl selection values until ItemsSource is set by @MrJul in Keep SelectingItemsControl selection values until ItemsSource is set #18634
• Fix Windows IME by @MrJul in Fix Windows IME #18645
• Fix crash when creating documents in an opened folder on android by @emmauss in Fix crash when creating documents in an opened folder on android #18651
• Fix MenuItem enabled state in the presence of sub-items. by @grokys in Fix MenuItem enabled state in the presence of sub-items. #18679

---

This discussion was created from the release 11.3.0-rc1.

[sn4k3]

Add XML doc comments to RegisterDirect warning about unsetValue

Good stuff.
just a few days ago I had a problem where my program crash due use a List of controls already have a visual parent. I took hours trying to find the problem where nothing make sense to me, all controls where new instances and added to list. It happens that my StyledProperty had the list initialized in the static register (unsetValue). Just then I realize that could be the cause, after remove the unsetValue and init the property in the constructor problem gone. It's not so obvious beside being a static property that unsetValue would share same instance across all instances of control.
I think this should also be in docs where StyledProperties are documented, as well as a sample how to handle such cases (Refererence types).

As for DirectProperty just notice now it also have an unsetValue, but the getter is required, being a DirectProperty our getter return the instance/value of it own object since it's a member. What are the case of use for unsetValue? If we always had to have an getter which returns the unique member?