[bisq-network/bisq] When not in the foreground as topmost app in Windows, bisq unexpectedly closes with a certain keystroke (#4882)

dav1dpgit notifications at github.com
Thu Dec 3 07:35:19 CET 2020


<!--
   SUPPORT REQUESTS: This is for reporting bugs in the Bisq app.
   If you have a support request, please join #support on Bisq's
   Keybase team at https://keybase.io/team/Bisq
-->

### Description
On a Windows PC with the bisq application open, synced and running, when a microsoft edge internet browser is also open and in the foreground (prioritized), the keystroke for closing the microsoft edge foreground browser somehow also closes the bisq application (at the same time.

**NOTE: I see the same keystroke will also close bisq when bisq is in the foreground.  This may or may not be the developers' intention, but the issue I am raising is the same keystroke will terminate bisq unexpectedly in a certain situation and not in the foreground.**

#### Version
Bisq version 1.5.0


### Steps to reproduce

Open bisq, and open Microsoft Edge browser.  Make the Microsoft Edge browser not a full screen, but not minimized, either.  This way both the Edge browser and bisq are visible on the same desktop or monitor.  Click the header bar of the Microsoft Edge browser to ensure it is in the foreground (and bisq is not the primary foreground application.)

Click Ctl-W to close the Edge browser and it will shut down.  At the same time, bisq is closed.


### Expected behaviour

Only the Microsoft Edge browser should have closed and bisq should have remained open.  When bisq is the 3rd deep application (1st = Microsoft Edge browser, 2nd = another Microsoft Edge browser, 3rd = bisq), the Ctl-W close command only closes the topmost application (the 1st Microsoft Edge browser,) all the rest, including bisq, continue to run.

### Actual behaviour

Both the topmost application and bisq both close.  Again, bisq should not have closed.


#### Device or machine

Microsoft Windows 10, most current version


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/issues/4882
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20201202/98a3f21f/attachment.htm>


More information about the bisq-github mailing list