Steven Kirk

The reason for using `StyledProperty` fields is current for performance: if the property were to be `AvaloniaProperty` typed then an extra cast would be required when getting/setting values. I think...

Thing is, failed bindings shouldn't crash an application: they don't in WPF, UWP, MAUI or any other XAML framework as far as I'm aware. We should definitely be logging an...

Yeah I've noticed the binding errors in `NativeMenuItem` but this happens because `NativeMenuItem` isn't a control and doesn't [override `LogBindingError` as `Visual` does](https://github.com/AvaloniaUI/Avalonia/blob/e99a95ecca8b19e1380b4be97cd3a71367a1585f/src/Avalonia.Visuals/Visual.cs#L488-L512). We need to fix this, but I...

I've taken more of a look into this, and the problem is that while in `Visual` we suppress binding errors before a control is attached to a tree, things like...

One option we discussed is returning `Point(double.NaN, double.NaN)` in this case, this has the advantage of not changing the API but the disadvantage of returning a value one may not...

Requires quite a major refactor of the binding system to be more context-aware I'm afraid. As mentioned in #5762 we suppress these warnings for controls, but bindings that don't apply...

In general we don't make "data" properties styleable, we only make "style" properties styleable (though there are some exceptions). `Slider.Value` should probably be made styleable to allow animations, but the...

To give some background: the reason we choose direct properties for "data" properties is mainly due to performance: - Styled properties are a lot slower than direct properties (direct properties...

The difference between 0.9.12 and 0.10.0 with the default theme is pretty big. However building it in R2R mode mostly offsets the difference. We suspect that this degradation in performance...

My next port of call was to try to work out just why the Fluent theme is so much slower. It's a much bigger more complex theme than Default of...