Version 5.3.0 generates XAML Binding error for some controls (like DatePicker) - wrong Style

[DrCQ]

Bug explanation

New Styles for the version 5.3.0 (compared to 5.2.1) contains the following line:

<Setter Property="AutomationProperties.Name" Value="{Binding Path=(wpf:HintAssist.Hint), RelativeSource={RelativeSource Self}, Converter={x:Static convertersInternal:AutomationPropertiesNameConverter.Instance}}" />

which cause the following XAML Binding error:

Error 4 DatePicker.(AutomationProperties.Name) Value 'null' cannot be assigned to property DatePicker.Name (type String).

In my opinion, the converter returns the wrong value type. I temporally fixed this problem while adding the following line to my Style definition:

<Setter Property="AutomationProperties.Name" Value=""/>

Version

5.3.0

[corvinsz]

@DrCQ perhaps you've mixed something up?
Version 5.3.0 was released on the 6th Oct 2025.
What you are talking about (the specific line + the AutomationPropertiesNameConverter) was introduced after version 5.3.0, on the 24th Oct 2025 (see #3946).

So basically the bug fix has not made it into a "full" release yet, but is already available in the pre-release versions (any version >5.3.0).
Please correct me if I am wrong.

[DrCQ]

@corvinsz Hi,
I just updated my old application from MD version 5.2.1 to 5.3.0 (using Nuget Package) without any changes in my code and faced the XAML Binding error (s. above).
In the next step, I looked at the current XAML Style of the DatePicker control and fund the mentioned AutomationProperties.Name line. My fast workaround was to explicitly set the value in my Style definition to avoid the Binding error. With this approach, I also fixed the Binding errors for TimePicker, ComboBox, TextBox etc.

The #3946 is known to me from other application. My workaround was to set for all related controls the Hint value. If this bug fix is planned for the next major release - fine. I can close this bug report.