diff options
| author | sky@google.com <sky@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2008-12-19 14:58:40 +0000 |
|---|---|---|
| committer | sky@google.com <sky@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2008-12-19 14:58:40 +0000 |
| commit | dc3785502ba13caa8680579d948f476cbb991f3a (patch) | |
| tree | 8291afa474499aab4550fa54686f0baca420db69 /chrome/browser/url_fetcher.cc | |
| parent | 159f77627c71bc666863cde38a358281d8b5fe0d (diff) | |
| download | chromium_src-dc3785502ba13caa8680579d948f476cbb991f3a.zip chromium_src-dc3785502ba13caa8680579d948f476cbb991f3a.tar.gz chromium_src-dc3785502ba13caa8680579d948f476cbb991f3a.tar.bz2 | |
Changes docking behavior to not offer a maximize drop target if there
is a maxmized tabbed browser on the monitor already. I don't feel this
is the right long term behavior, but until we figure that out I'm
going with this.
BUG=4878
TEST=maximize a tabbed browser, drag a tab out of the tabbed browser
toward the top of the screen and make sure you aren't offered a
dock target. Now restore the tabbed browser, drag a tab toward the
top of the screen and make sure you are offered a maximized drop
target.
Review URL: http://codereview.chromium.org/14858
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@7301 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/url_fetcher.cc')
0 files changed, 0 insertions, 0 deletions