Julien Lebosquain

API diff for review: ```diff namespace Avalonia.Input.Platform { public partial interface IClipboard { + System.Threading.Tasks.Task FlushAsync(); } } ```

Notes from the API review meeting: The API is accepted. The documentation should be updated to mention that not all platforms require this method, as some are auto-flushing.

> Was Avalonia designed from the ground up with a different layout logic than WPF? In Avalonia, you need `ClipToBounds=true` for this to work correctly. I've noticed that you opened...

I'm closing this for now as the PR has issues with failing tests, as mentioned before. Feel free to ping me to reopen when the problems are resolved.

The new test was passing on Windows but failing on Linux and macOS due to a floating point rounding error at the 6th decimal (17.14875030517578 vs 17.148752212524414). The tests were...

As discussed internally, this PR will probably be part of v12. Internal refactoring work is needed first to properly handle time on the compositor side.

I'm going to close this as we haven't seen the problem in months. We can revisit later if needed.

Thanks for your work, but I'm going to close this for now. As mentioned in https://github.com/AvaloniaUI/Avalonia/pull/16679#issuecomment-2287059126, DevTools are currently under a major internal refactoring and we won't accept impactful PRs...

Indeed, moving to AvaloniaVS (Rider has built-in *Go to definition* support for Avalonia).

During the API review, it was mentioned that a very similar feature already exists in `NumericUpDown`. We want to use a similar API shape for consistency. Note that a `NumericUpDown.CultureInfo`...