New issue
Advanced search Search tips

Issue 771716 link

Starred by 2 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug


Participants' hotlists:
Launcher-Polish


Sign in to add a comment

Swipe to pull up the launcher is incorrect when using multiple displays with touch

Project Member Reported by malaykeshav@chromium.org, Oct 4 2017

Issue description

Chrome Version: 63.0.3232.0

What steps will reproduce the problem?
(1) Connect an external touchscreen.
(2) Swipe open the app launcher on the external touchscreen

What is the expected result?
The launcher opens on the external screen

What happens instead?
The launcher opens on the internal screen


 
IMG_5576.MOV
26.4 MB Download
On further testing, this bug is specific to a touchscreen that is not perfectly (which is usually the case if calibrated manually from Settings>Display>Calibrate). The touch input location is translated to a point that is _just_ outside the bounds of the external screen.
Status: Assigned (was: Untriaged)
Cc: newcomer@chromium.org
Labels: Touch-Friendly-Launcher
Owner: minch@chromium.org

Comment 4 by minch@chromium.org, Oct 5 2017

Cc: malaykeshav@chromium.org
malaykesha@, why I can not repro the issue according to the repro steps? And what's settings>display>calibrate? Why I can not found it in the settings>display? (I didn't try it through multiple physical displays, what I did is to simulate two displays in Linux).
#4 
I havent tried this on linux. But you can try the following:
 - Translate the mouse clicks as touch via "--touch-devices"
 - Enable "--enable-touch-calibration-setting" to view the settings for the external monitor.

The calibrate settings is only visible if the system detects a touchscreen. But I am not sure how this would work on linux.


Labels: Touch-Friendly-Launcher-Triaged
Cc: minch@chromium.org
Owner: malaykeshav@chromium.org
This seems to be happening due to the GestureRecognizer falling back to the internal display incase the Swipe (or scroll) gesture event location lies outside the bounds of every screen.

Will have to look into it further.

Labels: -Pri-2 Pri-1
Owner: ----
Status: Untriaged (was: Assigned)
This was set to P1 but can't be easily reproduced? Is still an issue? Should the priority be lowered? Is seems very specific in that is will only happen if a device is manually recalibrated improperly? Should it actually be a WontFix in that case?
Owner: ginko@chromium.org
rewarding the initiative
Owner: ----
This one is difficult to reproduce, at least for me. The video shows a clear example, so I'll leave it open. I'm also not seeing a lot of listnr feedback about this right now.

Removing myself
Labels: -Pri-1 Pri-2
This is not a P1, trust me.
Status: Available (was: Untriaged)
Labels: -Pri-2 Pri-3
Downgrading to P3 as the use case seems to be somewhat exotic

Sign in to add a comment