robloo

I just ran across this one and agree this needs to be changed to follow WPF. Note that UWP and WinUI also search all dictionaries -- even merged ones --...

Something like this is a lot more helpful ```csharp /// /// Gets the first resource matching the given key within the application resources dictionary. /// /// The type of resource...

My understanding is at a framework level keyboard events should not be passed to disabled controls. That would solve the issues I see in the screen recording. It also shouldn't...

Seems to be a fairly fundamental issue. I'm surprised it has so far gone unnoticed except for the special cases. I see lots of examples: https://github.com/AvaloniaUI/Avalonia/pull/6632 https://github.com/AvaloniaUI/Avalonia/pull/7206

> I wonder what WPF does in this situation. Expected would be to unfocus element, but it's not clear what should be focused instead Here is a really nice write-up:...

> we can unfocus element if it gets disabled, but I'm not sure if this will be the correct approach. As far as I know, WPF don't do this. This...

@Takoooooo @maxkatz6 I'm waiting on the big styling updates branch to be merged before I do this. However, it still needs to be done before 11.0. If you want, just...

Now that all the control theme updates are made, I'm going to go through and update template parts within the next week or so.

Adding link to a specific discussion: https://github.com/AvaloniaUI/Avalonia/issues/3538#issuecomment-1141275108

Well, I had no visibility on the Preview 1 release date or I would have got this in. However, there is a draft PR now.