Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(321)

Issue 1366313003: Fix incorrect window show state after session restore. (Closed)

Created:
5 years, 2 months ago by shrike
Modified:
5 years, 2 months ago
Reviewers:
sky
CC:
chromium-reviews
Base URL:
https://chromium.googlesource.com/chromium/src.git@master
Target Ref:
refs/pending/heads/master
Project:
chromium
Visibility:
Public.

Description

Fix incorrect window show state after session restore. If a user quits Chrome with two windows, both docked, on restore Chrome will notice that neither window is fully visible and select the first window in its restoration list to make visible. However, the profile also has a notion of an active window, which session restore auto- matically makes fully visible. The result is that depending on the order in which the windows were placed in the dock, both windows can end up restored fully visible instead of only one of them (which ideally should be the last active window). This change causes session restore to restore the last active window to fully visible if all windows are hidden and the last active window appears in the window restoration list. BUG=536201 Committed: https://crrev.com/82b329e8cdbac775a5257989fd335d3e4641d713 Cr-Commit-Position: refs/heads/master@{#351164}

Patch Set 1 #

Patch Set 2 : Remove change from other cl. #

Total comments: 3
Unified diffs Side-by-side diffs Delta from patch set Stats (+6 lines, -2 lines) Patch
M chrome/browser/sessions/session_restore.cc View 1 chunk +6 lines, -2 lines 3 comments Download

Messages

Total messages: 9 (2 generated)
shrike
PTAL
5 years, 2 months ago (2015-09-25 22:19:03 UTC) #2
sky
https://codereview.chromium.org/1366313003/diff/20001/chrome/browser/sessions/session_restore.cc File chrome/browser/sessions/session_restore.cc (right): https://codereview.chromium.org/1366313003/diff/20001/chrome/browser/sessions/session_restore.cc#newcode393 chrome/browser/sessions/session_restore.cc:393: (*i)->window_id.id() == active_window_id) How is that the active window ...
5 years, 2 months ago (2015-09-28 14:54:05 UTC) #3
shrike
https://codereview.chromium.org/1366313003/diff/20001/chrome/browser/sessions/session_restore.cc File chrome/browser/sessions/session_restore.cc (right): https://codereview.chromium.org/1366313003/diff/20001/chrome/browser/sessions/session_restore.cc#newcode393 chrome/browser/sessions/session_restore.cc:393: (*i)->window_id.id() == active_window_id) On 2015/09/28 14:54:05, sky wrote: > ...
5 years, 2 months ago (2015-09-28 17:53:41 UTC) #4
sky
LGTM https://codereview.chromium.org/1366313003/diff/20001/chrome/browser/sessions/session_restore.cc File chrome/browser/sessions/session_restore.cc (right): https://codereview.chromium.org/1366313003/diff/20001/chrome/browser/sessions/session_restore.cc#newcode393 chrome/browser/sessions/session_restore.cc:393: (*i)->window_id.id() == active_window_id) On 2015/09/28 17:53:41, shrike wrote: ...
5 years, 2 months ago (2015-09-28 19:04:02 UTC) #5
commit-bot: I haz the power
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1366313003/20001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1366313003/20001
5 years, 2 months ago (2015-09-28 20:39:38 UTC) #7
commit-bot: I haz the power
Committed patchset #2 (id:20001)
5 years, 2 months ago (2015-09-28 21:23:24 UTC) #8
commit-bot: I haz the power
5 years, 2 months ago (2015-09-28 21:29:27 UTC) #9
Message was sent while issue was closed.
Patchset 2 (id:??) landed as
https://crrev.com/82b329e8cdbac775a5257989fd335d3e4641d713
Cr-Commit-Position: refs/heads/master@{#351164}

Powered by Google App Engine
This is Rietveld 408576698