summaryrefslogtreecommitdiffstats
path: root/url/url_canon_filesystemurl.cc
diff options
context:
space:
mode:
authormvrable@chromium.org <mvrable@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2013-04-24 01:41:17 +0000
committermvrable@chromium.org <mvrable@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2013-04-24 01:41:17 +0000
commit332eb31f571a103d729544362b6cf6c7a2307b46 (patch)
tree03b61152b4805024f87c98ca8c6d165899020198 /url/url_canon_filesystemurl.cc
parentb78f8f6cacba3b013d8bf9f33c4c5f27b9afb0a4 (diff)
downloadchromium_src-332eb31f571a103d729544362b6cf6c7a2307b46.zip
chromium_src-332eb31f571a103d729544362b6cf6c7a2307b46.tar.gz
chromium_src-332eb31f571a103d729544362b6cf6c7a2307b46.tar.bz2
Fix window-raise behavior
Chrome raises the browser window to the top of the window stacking order when it shouldn't: when opening a link in a new background tab, when opening a bookmarked page, etc. This likely hasn't gotten more attention since it's only noticeable on Linux when using a window manager that is not set to raise-on-click (a non-standard setting). The root cause is that Navigate will raise the window if called with params->window_action set to SHOW_WINDOW, and various places in the code set SHOW_WINDOW when they don't need to. Some calls to SHOW_WINDOW have been left, and the window will be raised in certain cases still: - When opening a singleton tab (such as the settings tab) in a different browser window than the current one. Opening the settings tab in the current window does not cause the window to be raised. - When invoking the Chrome binary to open new tab in an existing browser instance. BUG=87103 Review URL: https://chromiumcodereview.appspot.com/11421107 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@195973 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'url/url_canon_filesystemurl.cc')
0 files changed, 0 insertions, 0 deletions