Issue metadata
Sign in to add a comment
|
Command+Q with full screen app open and then clicking the chrome icon leads to interesting results |
||||||||||||||||||||||||
Issue description
Chrome Version : 63.0.3218.0
OS Version: OS X 10.12.6
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari 5:
Firefox 4.x:
IE 7/8/9:
What steps will reproduce the problem?
1. Have a bunch of Chrome tabs open.
2. Install Chrome remote desktop if needed.
3. Launch it.
4. Full screen the window by clicking on the funny diagonal arrow.
5. Tell OS X to keep CRD in the dock (not sure if this is needed).
6. Accidentally press Command+Q.
7. Chrome still shows as open (with an arrow below it in the dock)
8. Click on Chrome.
What is the expected result?
Windows restore on main desktop
What happens instead of that?
Windows restore in the full screen window of Chrome remote desktop.
Please provide any additional information below. Attach a screenshot if
possible.
UserAgentString: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3218.0 Safari/537.36
,
Sep 29 2017
[mac triage] Yeah, Dock integration for Chrome Apps currently sucks, but macOS doesn't offer the APIs that will allow us to do a better job. The CRD Dock icon is just a "shim" process - all it runs is the Dock icon, which is just a way to trigger the Chrome process to do things. This setup causes lots of stuff to break or work strangely.
,
Sep 29 2017
Unable to reproduce this issue on 63.0.3218.0 and on laetst canary 63.0.3227.0 using Mac 10.12.6 with steps mentioned below. 1.Launched chrome with 4 tabs opened. Installed Chrome Remote Desktop. 2.Launched CRD and clicked fullsceen button. 3.Now used Command+Q and observed chrome window with tabs opened. 4.Clicked on it. Nothing happens. Attaching screencast for reference. @Reporter: Could you please let us know what is expected behaviour here? and Could you tell whether we are missing anything in steps. Thanks !!
,
Oct 1
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 2
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by ligim...@chromium.org
, Sep 28 2017Labels: Needs-Bisect Needs-Triage-M63