- Wine-GitLab - list.winehq.org

[PATCH v3 0/1] MR10263: windows.web: Support JSON array and object parsing
by Olivia Ryan (＠olivi-r) March 6, 2026

March 6, 2026

Implements JsonArray, JsonObject value getters and extends JsonValue.Parse to support arrays and objects. -- v3: windows.web: Support JSON array and object parsing https://gitlab.winehq.org/wine/wine/-/merge_requests/10263

2 1

[PATCH 0/1] MR10263: windows.web: Support JSON array and object parsing
by Olivia Ryan (＠olivi-r) March 6, 2026

March 6, 2026

Implements JsonArray, JsonObject value getters and extends JsonValue.Parse to support arrays and objects. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10263

2 1

Re: [PATCH v4 0/3] MR10175: winmm/tests: Test a curated list of wave formats.
by Giovanni Mascellani (＠giomasce) March 6, 2026

March 6, 2026

On Wed Mar 4 11:22:01 2026 +0000, Giovanni Mascellani wrote: > Thanks, I'll have a look. !10262 should fix those, hopefully. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10175#note_131460

1 0

Re: [PATCH v2 0/2] MR10250: Call abort if _wassert error behavior is set to _OUT_TO_STDERR and trigger a debug break.
by Piotr Caban (＠piotr) March 6, 2026

March 6, 2026

Please also remove the FIXME message from `_set_abort_behavior`. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10250#note_131456

1 0

Re: [PATCH v2 0/2] MR10250: Call abort if _wassert error behavior is set to _OUT_TO_STDERR and trigger a debug break.
by Piotr Caban (＠piotr) March 6, 2026

March 6, 2026

Piotr Caban (@piotr) commented about dlls/msvcrt/exit.c: > else > fwprintf(stderr, L"Assertion failed: %ls, file %ls, line %d\n\n", str, file, line); > > - raise(SIGABRT); > - _exit(3); > + abort(); This matches with native behavior if `_OUT_TO_STDERR` is set but doesn't work as expected if `_OUT_TO_MSGBOX` is used. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10250#note_131455

1 0

Re: [PATCH v2 0/2] MR10250: Call abort if _wassert error behavior is set to _OUT_TO_STDERR and trigger a debug break.
by Piotr Caban (＠piotr) March 6, 2026

March 6, 2026

Piotr Caban (@piotr) commented about dlls/msvcrt/exit.c: > _cputs("\nabnormal program termination\n"); > } > #endif > + > +#if _MSVCR_VER > 0 > + if (MSVCRT_abort_behavior & _CALL_REPORTFAULT) > + DebugBreak(); I have tested it with ucrtbase and calling `DebugBreak` looks wrong. I'm getting 0xc0000409 exception. While the code of the exception may be misleading - this is the result of calling `fastfail(FAST_FAIL_FATAL_APP_EXIT)` (https://learn.microsoft.com/en-us/shows/inside/c0000409) I don't know what should happen if `fastfail` and I'm not sure if it's easily testable (maybe with msvcrt.dll if it behaves differently). `raise(SIGABRT)` should be called before handling `_CALL_REPORTFAULT` flag. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10250#note_131454

1 0

[PATCH v7 0/9] MR3048: Media.speech improvements.
by eric pouech (＠epo) March 6, 2026

March 6, 2026

This series adds a couple of features to WinRT's media.speech: - IVoiceInformation, and synthetizer's options are present (mainly use to store information, not yet to make fully use of it) - add a dummy implementation (1 single voice); that should be extended in future series by using ISpVoice instead - add a couple of more tests to go with implementation (the serie should prevent MS Flight simulator to crash on first connection. Crash is due to exception handling of C# generated exceptions from E_NOTIMPL with some X11 related critical resources). A+ -- v7: windows.media.speech: Implement get/put voice on synthesizer. windows.media.speech: Select a default voice in synthesizer. windows.media.speech/tests: Add more tests about default voice. windows.media.speech: Add basic implementation of IVoiceInformation. windows.media.speech: Implement IVectorView<VoiceInformation> on top of a stub provider. windows.media.speech/tests: Add tests about vector view's content. windows.media.speech/tests: Add more tests about IVoiceInformation. windows.media.speech: Add basic implementation on synthesizer options. windows.media.speech/tests: Add a couple of synthesizer's options tests. https://gitlab.winehq.org/wine/wine/-/merge_requests/3048

3 11

[PATCH v6 0/9] MR3048: Media.speech improvements.
by eric pouech (＠epo) March 6, 2026

March 6, 2026

This series adds a couple of features to WinRT's media.speech: - IVoiceInformation, and synthetizer's options are present (mainly use to store information, not yet to make fully use of it) - add a dummy implementation (1 single voice); that should be extended in future series by using ISpVoice instead - add a couple of more tests to go with implementation (the serie should prevent MS Flight simulator to crash on first connection. Crash is due to exception handling of C# generated exceptions from E_NOTIMPL with some X11 related critical resources). A+ -- v6: windows.media.speech: Implement get/put voice on synthesizer. https://gitlab.winehq.org/wine/wine/-/merge_requests/3048

3 10

[PATCH v5 0/9] MR3048: Media.speech improvements.
by eric pouech (＠epo) March 6, 2026

March 6, 2026

This series adds a couple of features to WinRT's media.speech: - IVoiceInformation, and synthetizer's options are present (mainly use to store information, not yet to make fully use of it) - add a dummy implementation (1 single voice); that should be extended in future series by using ISpVoice instead - add a couple of more tests to go with implementation (the serie should prevent MS Flight simulator to crash on first connection. Crash is due to exception handling of C# generated exceptions from E_NOTIMPL with some X11 related critical resources). A+ -- v5: windows.media.speech: Implement get/put voice on synthesizer. windows.media.speech: Select a default voice in synthesizer. windows.media.speech/tests: Add more tests about default voice. windows.media.speech: Add basic implementation of IVoiceInformation. windows.media.speech: Implement IVectorView<VoiceInformation> ontop of a stub provider. windows.media.speech/tests: Add tests about vector view's content. windows.media.speech/tests: Add more tests about IVoiceInformation. windows.media.speech: Add basic implementation on synthesizer options. windows.media.speech/tests: Add a couple of synthesizer's options tests. https://gitlab.winehq.org/wine/wine/-/merge_requests/3048

3 9

[PATCH 0/4] MR10261: Fix toolbar wrapping issues
by Ivan Ivlev (＠iviv) March 6, 2026

March 6, 2026

This MR resolves two bugs with toolbar wrapping I have discovered. 1. Toolbar missing four buttons when app window is maximized (wrap should not appear at all in this case). 2. Last toolbar button disappears when window size (toolbar size) is slightly narrower then button right border. Reasons of this behavior: 1. Toolbar buttons have BTNS_AUTOSIZE style, toolbar width is set using CCS_NORESIZE and equals to widths of all autosized buttons combined. cx (button width) value in TOOLBAR_WrapToolbar is set from nButtonWidth, which contains widest button width. Since buttons in toolbar have different widths, TOOLBAR_WrapToolbar miscalculates total width, because actual buttons widths are less then nButtonWidth. This results in TOOLBAR_WrapToolbar setting TBSTATE_WRAP when it is not not needed, and since app does not paint second button row, wrapped buttons just disappear. 2. After I fixed first issue, I noticed, that last button disappears, when toolbar become narrower then its right border. Then, when toolbar right border approximately in the middle of disappeared button, wrap happens. In windows system, wrapping occurs immediately when toolbar becomes narrower. Found solutions: 1. I noticed, that TOOLBAR_LayoutToolbar calculates buttons rects differently, thats because it checks if button have BTNS_AUTOSIZE style and then calculate size. So i moved this BTNS_AUTOSIZE size calculation in separate function for it to then be used in TOOLBAR_LayoutToolbar and TOOLBAR_WrapToolbar to guarantee that cx values for specific button will be equal in both functions. 2. TOOLBAR_WrapToolbar function decides to wrap in case `if ((x + cx - (infoPtr->nButtonWidth - infoPtr->nBitmapWidth) / 2 > width).` This `(infoPtr->nButtonWidth - infoPtr->nBitmapWidth) / 2` turns out, makes this gap, where button right border (x + cx) exceed toolbar right border (width), but wrap wont appear. I did not found any reasons to make this half-button gap, so I just removed it and it solved this issue. The comment above says /\* The layout makes sure the bitmap is visible, but not the button. \*/, but it was introduced in 1999, when TOOLBAR_LayoutToolbar did not existed, and I think its irrelevant now, since layout calculates cx taking both bitmap and string into account. I wrote tests for both fixes: 1. Creates CCS_NORESIZE toolbar, then add BTNS_AUTOSIZE buttons of different widths one by one and checks if wrap happened. In normal case (in windows) wrap should only happen on fourth button, but without fix wrap happens on third. 2. Creates CCS_NORESIZE toolbar with 4 BTNS_AUTOSIZE buttons. Toolbar width at the creation is calculated beforehand and equals exactly buttons widths combined. Then test reduces toolbar width by 1 and checks if wrap happened, in normal case wrap happens, without the fix its not. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10261

2 4