New issue
Advanced search Search tips

Issue 831267 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug

Blocking:
issue 822084



Sign in to add a comment

Cros splitscreen - Arc app window's resizability changes when trying to snap it

Project Member Reported by x...@chromium.org, Apr 10 2018

Issue description

Chrome Version: 67.0.3394.0
OS: Chrome

What steps will reproduce the problem?
(1) With this CL https://chromium-review.googlesource.com/c/chromium/src/+/1005728 in place (the CL is trying to fix Issue 822084)
(2) Open a resizable ARC app
(3) Enter tablet mode, enter overview, drag the ARC app window to snap it

What is the expected result?
The ARC app window should be snapped successfully

What happens instead?
The ARC app window is snapped at first for a very short time and then is maximized. Split view mode is ended.




 

Comment 1 by x...@chromium.org, Apr 10 2018

Another thing I noticed that may also be related:
Steps:
1) Open a Chrome browser and two resizable ARC apps (e.g., Play store, Settings)
2) Enter tablet mode and enter overview mode, drag the browser window to snap to one side of the screen
3) Select one of the two Arc apps to snap to the other side of the screen (interestingly, in this case Arc App window can be snapped)
4) Tap on the shelf icon of the other Arc app, it should replace the old snapped ARC app and is now snapped too
5) Now quickly tapping on the two shelf icons of the two ARC apps alternantly

At some point the ARC app is maximized and split view mode is ended.

Comment 2 by mukai@chromium.org, Apr 11 2018

Status: Started (was: Assigned)

Comment 3 by mukai@chromium.org, Apr 12 2018

The window reports itself not resizable exactly in the transition of snapping. Seems like a bug on ARC to sending such status.

Comment 4 by mukai@chromium.org, Apr 13 2018

Status: Fixed (was: Started)
The fix was merged on ARC++.

Comment 5 by x...@chromium.org, Apr 13 2018

Thanks! I'll go ahead and send the CL to fix Issue 822084 to review.

Sign in to add a comment