Issue metadata
Sign in to add a comment
|
Cannot select and activate pinned v2app through shelf context menu |
||||||||||||||||||||||
Issue descriptionChrome Version: 57.0.2951.0 dev (64-bit) OS: ChromeOS Panther What steps will reproduce the problem? (1) Open a Chrome App (e.g. Chrome Remote Desktop, Files) that supports multiple windows. (2) Right-click on the app icon in the task bar, and select New Window. (3) Minimize the second window. (4) Click to focus the first window. (5) Left-click the app icon and click on the entry for the second window. What is the expected result? Expect that the second window is restored. What happens instead? Nothing happens; it seems that the first window may be getting re-restored, except that it is already focused so there's no visible effect.
,
Jan 3 2017
,
Jan 9 2017
wez@ at what point was this working? 55?
,
Jan 9 2017
I believe it broke with an M57 dev-channel push; IIRC it worked fine in M56.
,
Jan 11 2017
,
Jan 11 2017
I may have caused this regression; I'd like a bisect if possible.
,
Jan 11 2017
Can someone check if this is just an unexpected window ordering in the menu? At repro step (5), if I click the top item, it *does* restore the 2nd window.
,
Jan 11 2017
Ah, nevermind, that ordering might be expected. I simply missed [implicit] step (0) Pin the app to your shelf before opening.
,
Jan 11 2017
Re #7: I have two Chrome Remote Desktop windows open right now, one on top of the other. If I click on the pinned taskbar icon then whichever CRD window last had focus is immediately raised to the front. If I then select one of the windows from the context menu, nothing happens regardless of which one.
,
Jan 11 2017
I can confirm that this issue only repros if the app is pinned; sorry, didn't think to mention that.
,
Jan 12 2017
,
Jan 13 2017
Your change meets the bar and is auto-approved for M56. Please go ahead and merge the CL manually. Please contact milestone owner if you have questions. Owners: amineer@(clank), cmasso@(bling), gkihumba@(cros), bustamante@(desktop) For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 14 2017
Tested on 56.0.2924.63, bug is not seen on M-56. It is on M-57 only. So remove RBS mark, and we do not need to do a merge.
,
Jan 24 2017
Verified on Chrome OS 9202.1.0, 57.0.2987.6
,
Mar 3 2017
,
Mar 3 2017
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by w...@chromium.org
, Dec 22 2016