https://bugs.winehq.org/show_bug.cgi?id=43711
Sebastian Lackner sebastian@fds-team.de changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.winehq.org/sho | |w_bug.cgi?id=39440 Product|Wine-staging |Wine Component|-unknown |-unknown
--- Comment #1 from Sebastian Lackner sebastian@fds-team.de --- You opened this bug report in the Wine Staging category, but I do not see how this should be a Wine Staging regression. Moving to the Wine product.
Besides that, reparenting windows without sending proper messages is expected to cause problems. Wine expects that applications correctly follow the XEMBED protocol. It would be more useful to focus your investigation on this part. What is the problem with XEMBED? And can you provide a simple testcase without involving a lot of third party components?
Please note that Pipelight (deprecated now) has been using Wine + XEMBED successfully for a couple of years already. Most of the time when people experience issues with XEMBED, the real issue is that Linux apps do not correctly follow the XEMBED protocol. QT widgets for example have multiple bugs and pass invalid parameters in their notification messages.