New issue
Advanced search Search tips

Issue 823991 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Command-line --new-window --window-position ignores coordinates of second browser window

Reported by to.vss....@gmail.com, Mar 21 2018

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36

Steps to reproduce the problem:

1. Call "chrome.exe --new-window --window-position=0,0 http://localhost/monitor1.html --start-fullscreen"
2. Call "chrome.exe --new-window --window-position=1920,140 http://localhost/monitor2.html --start-fullscreen"

This is a kiosk-like application w/ no user input.

What is the expected behavior?
Both monitors would have an instance of Chrome in fullscreen showing the HTML pages passed in.

What went wrong?
The second instance of Chrome ignores the x,y coordinates and opens in the same monitor as the first. The second browser follows the first w/ or w/o the '--start-fullscreen' argument.

I tried several different variations of my Powershell launch script, and even put sleeps between the calls. Nothing worked as expected for the second browser (the first browser did work). It does not matter if I try to load the monitor-1 (0,0) or monitor-2 (1920,140) first. The second browser always opens on the same monitor as the first.

Did this work before? N/A 

Chrome version: 64.0.3282.186  Channel: n/a
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: 

There does not appear to be a category for this type of bug. I first tried the "API" section, but no categories seemed to apply.

Windows has two monitors extended like this:

---------------------------------
|                                |
|                                |
|                                |
|                                ||-------------------------|
|          Monitor 1             ||                         |
|                                ||                         |
|                                ||                         |
|                                ||      Monitor 2          |
|                                ||                         |
|                                ||                         |
-------------------------------------------------------------
 
Labels: Needs-Triage-M64
Components: -Platform>DevTools UI>Browser
Cc: rbasuvula@chromium.org
Labels: TE-NeedsTriageHelp
As per issue description need to access the localhost urls. Unable to access the provided URL from TE end, hence adding the respective label for it to  triage further.

Thank You!
The URL is for example only. You can link to any website using the API. For example:

1. Call "chrome.exe --new-window --window-position=0,0 https://bugs.chromium.org/hosting/ --start-fullscreen"
2. Call "chrome.exe --new-window --window-position=1920,140 https://bugs.chromium.org/p/chromium/issues/ --start-fullscreen"

You could even use file://test1.html and file://test2.html instead.

The issue revolves around the need to open up the second browser on a different monitor. Even though the API clearly should support this behavior it fails to work. It should be able to handle any multiple monitor layout as long as you understand where 0,0 is and the rest of the layout.
Cc: kkaluri@chromium.org
Labels: Hotlist-DesktopUIChecked Target-72 M-72 FoundIn-64 Hotlist-DesktopUIValid
Status: Untriaged (was: Unconfirmed)
*** Mass UI Triage ***

Able to reproduce the issue on Windows 10, Debian Rodete with chrome #72.0.3616.0 and also on earlier M60 Build #60.0.3112.0, this is a non-regression issue.

Sign in to add a comment