https://bugs.winehq.org/show_bug.cgi?id=40828
--- Comment #15 from Robert Walker bob.mt.wya@gmail.com --- (In reply to Olivier F. R. Dierick from comment #14)
So, the fix is to NOT push the taskbar to the top of the z order in any case. There is no drawback because the taskbar has never stuck 'above all windows' anyway.
I've also taken a look at this issue. Even when the taskbar is drawn below a fullscreen game window, it is able to erroneously capture keypresses. This is a known issue with Doom 2016. Hamish's patch will provide a complete fix for this problem as well. Since the taskbar will not be drawn at all, if a window is fullscreen.
If the taskbar is not drawn on top of the Z-order stack then maximising a window will draw on top of the taskbar (which does not mimic native MS Windows behaviour). I've tested out a few scenarios, with a small C++ test program (compiled with winegcc) which simply draws a window. One the tests being to maximise the window.