[Bug 50202] New: Blue Oath: Update/Event pop-up window explodes; fills entire screen instead of correct size

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=50202

Bug ID: 50202
           Summary: Blue Oath: Update/Event pop-up window explodes; fills
                    entire screen instead of correct size
           Product: Wine
           Version: 5.22
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

Created attachment 68715
  --> https://bugs.winehq.org/attachment.cgi?id=68715
Trace/Execution log and screenshots showing the problem.

When running Blue Oath, a Unity Engine-powered game for Microsoft Windows, the
game checks for updates from its server. When an update is found, the game
usually throws up a event banner or update news banner. This is done via the
game spawning a child browser-like window (I don't know the exact term, but
it's like a floating window normally parented to the main window). On Windows
10, this works fine and will show information about the game. In Wine 5.22
(installed on Arch Linux, NOT wine-staging) this child window fills up the
entire screen.

Do note that Wine 5.2-staging does somewhat show content in the Window, but
it's corrupted (just random garbage).

I have included an ZIP archive to this bug report containing logs and WINE
mentioning things like "fixme". To replicate this, you can download the game
from this page, https://clsyjp.blueoath.com/download.html and then extract the
ZIP file to wherever. Then, look inside the blueoath folder for a EXE file
called blueoath.exe. If you have the EXE icon previews enabled, the icon looks
like a blonde long-haired girl with a hat smiling at you.

There is also another bug where the game does not respond to clicks that I
think is related to Unity and/or how WINE is doing something, but I believe
that would be better suited for another bug.

If you need additional information, I can provide that for you - just let me
know. Let's see if we can get this bug squashed. :)