Garry Avalonia already has an open issue describing the same behaviour: AvaloniaUI/Avalonia#14167. There is no released upstream fix yet, so I’ve set up a daily task to monitor for any substantive updates.
A bug filed nearly 3 years ago. You may be monitoring for a long time.
This is what happens (by default anyway) when a framework or OS-level product gets big enough and established enough -- minor bugs get tolerated for too long (IMO). I don't realistically expect you to keep up this pace forever with Objo, especially because I'd expect the volume of bugs to stabilize at a relatively low level as the product matures under real-world usage; it's still early days. But I know your vision is to not let this kind of thing happen, either.
At least Avalonia is MIT open source, so if push comes to shove you can fix it yourself (or one of us can). In fact I wonder if open source products often don't sort of fall into that sort of prioritizing -- that is, no pull requests = no one cares. Question the longstanding nature of the bug, you get a shrug and the invitation to fix it yourself.
Somewhere on the glide path to my upcoming dotage, I might fill some of my time on FOSS projects -- until then, I can't say how common that might be, as I haven't got experience with it.