This message is *very* noisy and totally dominates +win (e.g. it printed 1.5 million times in a relatively short log of a Steam session). Is it useful? If so, perhaps we could log only around the error conditions?
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/8762
This is for documents with multiple frames that are loaded asynchronously.
--
v2: mshtml/nsio: Fire BeforeNavigate2 event in async_open.
ieframe/tests: Add test for iframes.
https://gitlab.winehq.org/wine/wine/-/merge_requests/8727
See also the linked bug report, but the short description is that some wine-only fake device was removed at some point, and winecfg's audio tab was never updated to handle that situation. This MR fixes that problem by using real devices and filling in some data structures to make that work.
I'm marking this as a draft so that others can suggest improvements or alternatives, as I'm not sure if this means of doing it is acceptable to Wine.
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=58204
--
v5: winecfg: Fix audio tab by fetching the default device's audio driver.
mmdevapi: Set DEVPKEY_Device_Driver during MMDevice_Create().
https://gitlab.winehq.org/wine/wine/-/merge_requests/8679
This has been implemented in a few different ways (see MR !7238 and MR !359), neither of which have associated tests.
This way of doing things sidesteps the need to update existing `VT_BLOB` properties by just storing/retrieving them in the same format we always have. If the registry data doesn't match a set of criteria, we treat it as `VT_BLOB` always.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/8760
uiLengthDrawn should represent the number of characters that have been processed.
However, the original implementation uses len (the count of displayed characters
in the current line), which is not accurate.
When text requires line breaks or special processing (such as adding an ellipsis),
the actual number of processed characters may differ from the number of displayed
characters.
When the DT_CALCRECT flag is absent, len gets decremented to 0 during the drawing loop.
Consequently, uiLengthDrawn becomes inaccurate since it relies on len's value for statistics.
--
v7: user32: Fix uiLengthDrawn calculation in DrawTextExW().
https://gitlab.winehq.org/wine/wine/-/merge_requests/8178