How to launch Brave on the active monitor

Description of the issue:

On multi-monitor Ubuntu Linux (any version), Brave opens on the last monitor where it was used. In other words, if Brave was used on monitor #2, when Brave is launched again, regardless whether Brave is currently open or closed, including when the system has rebooted, Brave always opens again on monitor #2. If an open Brave instance is dragged from monitor #2 to monitor #1 and closed, then the next time it launches, it will launch on monitor #1. It appears that Brave simply loads its last state.

How can this issue be reproduced?

  1. Launch Brave using a desktop or panel launcher icon on monitor #1 and observe which monitor the browser appears on.
  2. Close Brave.
  3. Launch Brave using a desktop or panel launcher icon on monitor #2 and observe which monitor the browser appears on.

Expected result:

Launching Brave using a desktop icon or any other shortcut from a given monitor should load Brave on that monitor.
Additionally, launching Brave from the command line should simply open on the active monitor.

Brave Version( check About Brave):

Version 1.37.116 Chromium: 100.0.4896.127 (Official Build) (64-bit)

Additional Information:

It makes sense that remembering the last state of the browser is desired over just always launching on one particular monitor. Chrome also appears to use the same behavior as Brave, but there should be a way to override this behavior. Applications, including other browsers, tend to open on the monitor that they were launched from. This is not always the case, but it is more intuitive behavior.
On multi-monitor systems, the extra step of having to drag the window to the desired monitor is quite annoying. Especially when juggling remote desktop windows, terminal windows, word processor windows, etc.

Is there a better way to get assistance with this issue?

Considering it sounds like Chrome works the same way, I think the best bet would be to check whether there’s an issue already filed against Chromium; and if not, file one there so it can be addressed upstream. It sounds like this behavior is likely to have been inherited from Chromium.