|
|
Chromium Code Reviews|
Created:
3 years, 10 months ago by Qiang(Joe) Xu Modified:
3 years, 10 months ago CC:
chromium-reviews, tfarina Target Ref:
refs/pending/heads/master Project:
chromium Visibility:
Public. |
Descriptioncros: Disable the auto management logic for v1app browser window
Changes:
(1) For "open as window" browser window (v1app window), we disable auto management logic. So that they can restore the saved window bounds, not interrupted by auto placement such as centering window in work area.
(2) Simplify BrowserRemembersDockedState to test only state not bounds for reasons (a) bounds logic for app or tabbed browser window is tested in added test coverage, (b) this test will soon be removed in M-58 because of deprecation of docked window on Chrome OS.
BUG=687385
TEST=emulator tests show that v1app bounds restoring works just like v2 apps; also test coverage is added.
Review-Url: https://codereview.chromium.org/2690563005
Cr-Commit-Position: refs/heads/master@{#450216}
Committed: https://chromium.googlesource.com/chromium/src/+/2fc42ea7b1264dc128a1e454d92eebc25e1076c5
Patch Set 1 #Patch Set 2 : fix test failure and add test coverage #Patch Set 3 : scope tests to OS_CHROMEOS #
Total comments: 6
Patch Set 4 : based on ps3's comments #
Total comments: 2
Patch Set 5 : browser_frame_ash_browsertest #
Total comments: 6
Patch Set 6 : nits #
Messages
Total messages: 33 (23 generated)
The CQ bit was checked by warx@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: linux_chromium_chromeos_ozone_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
Description was changed from ========== cros: Disable the auto management logic for v1app browser window BUG=687385 TEST=emulator tests ========== to ========== cros: Disable the auto management logic for v1app browser window BUG=687385 TEST=emulator tests ==========
warx@chromium.org changed reviewers: + oshima@chromium.org, sky@chromium.org
Description was changed from ========== cros: Disable the auto management logic for v1app browser window BUG=687385 TEST=emulator tests ========== to ========== cros: Disable the auto management logic for v1app browser window Changes: (1) For "open as window" browser window (v1app window), we disable auto management logic. So that they can restore the saved window bounds, not interrupted by auto placement such as centering window in work area. (2) Simplify BrowserRemembersDockedState to test only state not bounds for reasons (a) bounds logic for app or tabbed browser window is tested in added test coverage, (b) this test will soon be removed in M-58 because of deprecation of docked window on Chrome OS. BUG=687385 TEST=emulator tests show that v1app bounds restoring works just like v2 apps; also test coverage is added. ==========
The CQ bit was checked by warx@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Hi all, ptal, thanks!
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: win_chromium_rel_ng on master.tryserver.chromium.win (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)
The CQ bit was checked by warx@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
https://codereview.chromium.org/2690563005/diff/40001/chrome/browser/ui/views... File chrome/browser/ui/views/frame/browser_view_interactive_uitest.cc (right): https://codereview.chromium.org/2690563005/diff/40001/chrome/browser/ui/views... chrome/browser/ui/views/frame/browser_view_interactive_uitest.cc:66: IN_PROC_BROWSER_TEST_P(BrowserViewTestParam, Why does this need to be in interactive tests? https://codereview.chromium.org/2690563005/diff/40001/chrome/browser/ui/views... chrome/browser/ui/views/frame/browser_view_interactive_uitest.cc:80: ASSERT_TRUE(browser); We don't assert that new returns non-null. If new fails chrome crashes. https://codereview.chromium.org/2690563005/diff/40001/chrome/browser/ui/views... chrome/browser/ui/views/frame/browser_view_interactive_uitest.cc:102: ASSERT_TRUE(browser); Same comment about checking return value from new.
Hi all, ptal, thanks! https://codereview.chromium.org/2690563005/diff/40001/chrome/browser/ui/views... File chrome/browser/ui/views/frame/browser_view_interactive_uitest.cc (right): https://codereview.chromium.org/2690563005/diff/40001/chrome/browser/ui/views... chrome/browser/ui/views/frame/browser_view_interactive_uitest.cc:66: IN_PROC_BROWSER_TEST_P(BrowserViewTestParam, On 2017/02/13 17:43:03, sky wrote: > Why does this need to be in interactive tests? It doesn't need. I moved it to browser_browsertest.cc. https://codereview.chromium.org/2690563005/diff/40001/chrome/browser/ui/views... chrome/browser/ui/views/frame/browser_view_interactive_uitest.cc:80: ASSERT_TRUE(browser); On 2017/02/13 17:43:03, sky wrote: > We don't assert that new returns non-null. If new fails chrome crashes. Done. https://codereview.chromium.org/2690563005/diff/40001/chrome/browser/ui/views... chrome/browser/ui/views/frame/browser_view_interactive_uitest.cc:102: ASSERT_TRUE(browser); On 2017/02/13 17:43:03, sky wrote: > Same comment about checking return value from new. Done.
The CQ bit was checked by warx@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
https://codereview.chromium.org/2690563005/diff/60001/chrome/browser/ui/brows... File chrome/browser/ui/browser_browsertest.cc (right): https://codereview.chromium.org/2690563005/diff/60001/chrome/browser/ui/brows... chrome/browser/ui/browser_browsertest.cc:2963: // Test that in Chrome OS, for app browser (v1app) windows, the auto management We try to avoid platform specific code in c/b/ui. Platform specific code goes in the appropriate subdirectories. So, how about putting this in browser_frame_ash_browsertest?
The CQ bit was checked by warx@chromium.org to run a CQ dry run
Hi all, ptal, thanks! https://codereview.chromium.org/2690563005/diff/60001/chrome/browser/ui/brows... File chrome/browser/ui/browser_browsertest.cc (right): https://codereview.chromium.org/2690563005/diff/60001/chrome/browser/ui/brows... chrome/browser/ui/browser_browsertest.cc:2963: // Test that in Chrome OS, for app browser (v1app) windows, the auto management On 2017/02/13 23:35:51, sky wrote: > We try to avoid platform specific code in c/b/ui. Platform specific code goes in > the appropriate subdirectories. So, how about putting this in > browser_frame_ash_browsertest? sure, updated.
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
LGTM - but wait for Oshima. https://codereview.chromium.org/2690563005/diff/80001/chrome/browser/ui/views... File chrome/browser/ui/views/frame/browser_frame_ash_browsertest.cc (right): https://codereview.chromium.org/2690563005/diff/80001/chrome/browser/ui/views... chrome/browser/ui/views/frame/browser_frame_ash_browsertest.cc:20: }; private: DISALLOW...
lgtm with nits https://codereview.chromium.org/2690563005/diff/80001/chrome/browser/ui/views... File chrome/browser/ui/views/frame/browser_frame_ash_browsertest.cc (right): https://codereview.chromium.org/2690563005/diff/80001/chrome/browser/ui/views... chrome/browser/ui/views/frame/browser_frame_ash_browsertest.cc:19: bool TestApp() { return GetParam(); } nit: CreateV1App() would be better https://codereview.chromium.org/2690563005/diff/80001/chrome/browser/ui/views... chrome/browser/ui/views/frame/browser_frame_ash_browsertest.cc:54: EXPECT_EQ(original_bounds.ToString(), window->bounds().ToString()); nit: no need to convert to string. (Old tests use this and they need to be updated)
done, thanks for review https://codereview.chromium.org/2690563005/diff/80001/chrome/browser/ui/views... File chrome/browser/ui/views/frame/browser_frame_ash_browsertest.cc (right): https://codereview.chromium.org/2690563005/diff/80001/chrome/browser/ui/views... chrome/browser/ui/views/frame/browser_frame_ash_browsertest.cc:19: bool TestApp() { return GetParam(); } On 2017/02/14 01:09:51, oshima wrote: > nit: CreateV1App() would be better Done. https://codereview.chromium.org/2690563005/diff/80001/chrome/browser/ui/views... chrome/browser/ui/views/frame/browser_frame_ash_browsertest.cc:20: }; On 2017/02/14 00:38:27, sky wrote: > private: DISALLOW... Done. https://codereview.chromium.org/2690563005/diff/80001/chrome/browser/ui/views... chrome/browser/ui/views/frame/browser_frame_ash_browsertest.cc:54: EXPECT_EQ(original_bounds.ToString(), window->bounds().ToString()); On 2017/02/14 01:09:51, oshima wrote: > nit: no need to convert to string. (Old tests use this and they need to be > updated) Done.
The CQ bit was checked by warx@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from oshima@chromium.org, sky@chromium.org Link to the patchset: https://codereview.chromium.org/2690563005/#ps100001 (title: "nits")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
CQ is committing da patch.
Bot data: {"patchset_id": 100001, "attempt_start_ts": 1487035200956490,
"parent_rev": "f1ebc3e6a38846d528181d052d496ba1524a1982", "commit_rev":
"2fc42ea7b1264dc128a1e454d92eebc25e1076c5"}
Message was sent while issue was closed.
Description was changed from ========== cros: Disable the auto management logic for v1app browser window Changes: (1) For "open as window" browser window (v1app window), we disable auto management logic. So that they can restore the saved window bounds, not interrupted by auto placement such as centering window in work area. (2) Simplify BrowserRemembersDockedState to test only state not bounds for reasons (a) bounds logic for app or tabbed browser window is tested in added test coverage, (b) this test will soon be removed in M-58 because of deprecation of docked window on Chrome OS. BUG=687385 TEST=emulator tests show that v1app bounds restoring works just like v2 apps; also test coverage is added. ========== to ========== cros: Disable the auto management logic for v1app browser window Changes: (1) For "open as window" browser window (v1app window), we disable auto management logic. So that they can restore the saved window bounds, not interrupted by auto placement such as centering window in work area. (2) Simplify BrowserRemembersDockedState to test only state not bounds for reasons (a) bounds logic for app or tabbed browser window is tested in added test coverage, (b) this test will soon be removed in M-58 because of deprecation of docked window on Chrome OS. BUG=687385 TEST=emulator tests show that v1app bounds restoring works just like v2 apps; also test coverage is added. Review-Url: https://codereview.chromium.org/2690563005 Cr-Commit-Position: refs/heads/master@{#450216} Committed: https://chromium.googlesource.com/chromium/src/+/2fc42ea7b1264dc128a1e454d92e... ==========
Message was sent while issue was closed.
Committed patchset #6 (id:100001) as https://chromium.googlesource.com/chromium/src/+/2fc42ea7b1264dc128a1e454d92e... |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
