Scaling factor from CLI not working

[rickalex21]

Description

I have two monitors, I would like to open brave scaled to a factor of 1 on one
monitor and a factor of 2 on the other monitor. The problem is that when I try to
open another brave window it uses the same session and I get the same scaling. I get
this message:

Opening in existing browser session.

How can I open a new session of brave from the command line using another scale
factor when a session is already running? I already tried using --user-data-dir and
that did not help, it opens the scaled one instead of a new scaled one. If I do get
this working then it's up to me to figure out how to get the focused monitor on
wayland using river and execute the correct command bellow.

I looked at all the flags here and I don't see something like --new-session.

#!/bin/bash
brave_X11(){
   dbus-launch ~/.local/share/brave/brave  --disable-gpu
}
brave_wayland(){
  # monitor 1 
  # dbus-launch ~/.local/share/brave/brave --high-dpi-support=1 --force-device-scale-factor=2
  # monitor 2
  dbus-launch ~/.local/share/brave/brave --user-data-dir="$HOME/.config/BraveSoftware/Brave-Browser" --high-dpi-support=1 --force-device-scale-factor=1

}

if [ "$XDG_SESSION_TYPE" == "wayland" ];then brave_wayland else brave_X11 ;fi 

Steps to Reproduce

1. Open brave from the command line using flags --high-dpi-support=1 --force-device-scale-factor=2
2. Open brave again from the command line but using a factor of 1.

It will use the same scale factor instead of the new one provided.

Actual result:

Both windows are scaled the same.

Expected result:

Windows should be scaled differently.

Reproduces how often:

Every time.

Brave version (brave://version info)

Brave 1.56.20 Chromium: 115.0.5790.171 (Official Build) unknown (64-bit)
Revision cf9067bf10d8f798c24643029af1d24e275646d6-refs/branch-heads/5790@{#1924}
OS Linux
JavaScript V8 11.5.150.22
User Agent Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36
Command Line /home/ritchie/.local/share/brave/brave --user-data-dir=/home/ritchie/.config/BraveSoftware/Brave-Browser --high-dpi-support=1 --force-device-scale-factor=1 --disable-domain-reliability --enable-dom-distiller --origin-trial-public-key=bYUKPJoPnCxeNvu72j4EmPuK7tr1PAC7SHh8ld9Mw3E=,fMS4mpO6buLQ/QMd+zJmxzty/VQ6B1EUZqoCU04zoRU= --sync-url=https://sync-v2.brave.com/v2 --lso-url=https://no-thanks.invalid --variations-server-url=https://variations.brave.com/seed --variations-insecure-server-url=https://variations.brave.com/seed --flag-switches-begin --flag-switches-end --component-updater=url-source=https://go-updater.brave.com/extensions
Executable Path /home/ritchie/.local/share/brave/brave
Profile Path /home/ritchie/.config/BraveSoftware/Brave-Browser/Default

Version/Channel Information:

• Can you reproduce this issue with the current release? Yes
• Can you reproduce this issue with the beta channel? N/A
• Can you reproduce this issue with the nightly channel? N/A

Other Additional Information:

• Does the issue resolve itself when disabling Brave Shields? N/A
• Does the issue resolve itself when disabling Brave Rewards? N/A
• Is the issue reproducible on the latest version of Chrome? N/A

Miscellaneous Information:

I'm running Void Linux with Wayland.

[tpaniaki]

Those options seem indeed to be ineffective on wayland. Any developpement?