On Sun Apr 26 14:32:21 2026 +0000, Dmitry Timoshkov wrote:
The tests that I marked as todo_wine were added by me long time ago for completeness, they don't replicate something that I observed in real applications. It's pretty unlikely that an application would provide a rectangle which is intentionally very small for the provided text, and depend on how the text could be clipped in that rectangle. Quoting https://gitlab.winehq.org/wine/wine/-/merge_requests/9775#note_136717: I had to mark some of the tests that rely on strange GdipMeasureCharacterRanges() logic for cases when the string doesn't fit onto the provided bounds as todo_wine in last commit since I couldn't figure out how it's supposed to work, that could be investigated separately. Do you have a reason to worry about these particular tests being marked as todo? Generally I would like to reach full compatibility with native libraries. I know that sometimes it is not possible, but it is only my vision of Wine libraries.
If this test case has low priority, then it is ok for me to introduce `todo_wine`. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/9775#note_137694