Issue 15672  has been merged into this issue.

from  issue 15672 

Adam.Walling wrote:
The "Local State" file in Chromium, under the "browser"->"window_placement" object, I 
can see that the "left" value is being saved incorrectly. So now we know the problem 
is 
in the code saving the window placement, not the code restoring it. What is strange 
is 
that it works around -540 or so, but once it gets lower than somewhere near that 
number, it starts to exhibit this bad behavior and save a value significantly lower 
than it should (for example, i started it up and it was at -400, moved it maybe 200 
or 
300 pixels to the left, so it should be ~ -700, but instead it was saved as more than 
-
2000!!)

 Issue 16075  has been merged into this issue.

 Issue 16131  has been merged into this issue.

this also happens to me. it first started with 3.0.191.3
Windows XP dual monitors

the startup window placement is almost entirely offscreen to the right edge of the 
right monitor

I think this is due to Yuzo's changes either in r17233, r18795, or r19012.

Yuzo, when fixing, can you check the various duped bugs?  There may be multiple issues 
here.

 Issue 16152  has been merged into this issue.

Do you guys plan on updating the dev channel before this issue is fixed?

I just verified the regression cl is r19012

Sorry for the regression. I've started working on this.

Yuzo

 Issue 16151  has been merged into this issue.

I have the same problem and I have figured out how to reliably reproduce it.

I have Windows XP with two 1280x1024 monitors.

If I close Chrome on my primary monitor (the left monitor, internally Display #2, 
don't ask, nVidia drivers like to screw up display numbering FOREVER) it reopens in 
the correct position.  If I close it on my non-primary monitor (the right monitor, 
internally Display #1), the Y position is properly preserved, but the X is not.  When 
I reopen it only about 30 pixels of the window's width are visible on the right side 
of the non-primary monitor.

I just discovered this posting.  I filed this early this morning: 
http://code.google.com/p/chromium/issues/detail?id=16185
It seems to be the same issue.  I discovered the same issue with Local State.  My new 
bug should probably be merged with this one.
Cheers,
m.f

When closing chrome on 1 monitor with the right side off screen, it reposition itself at startup so 
that the whole window is visible on first screen. (It moves to the rightest on first screen)

_________________________________     _________________________________
|        _______|_____          |     |  ____________ |               |
|       |       | _[]x|         |     | |        _[]x||               |
|       |       |     |         |     | |            ||               |
|       |       |     |         | --> | |            ||               |
|       |_______|_____|         |     | |____________||               |
|               |               |     |               |               |
|               |               |     |               |               |
---------------------------------     ---------------------------------

When chrome is more than half out of screen it reappear on the right screen, but instead of reposition 
to the leftest on the second screen, it goes right.

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=20246 

------------------------------------------------------------------------
r20246 | yuzo@chromium.org | 2009-07-08 21:58:29 -0700 (Wed, 08 Jul 2009) | 11 lines
Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/src/views/window/window_win.cc?r1=20246&r2=20245

Fix: Position always off-screen when starting up

Fixed the offset-by-taskbar logic.

Tested with dual monitors, trying left-right and up-down monitor layouts.

TEST=Use dual monitors (first:left, second:right) and open, close, and reopen Chromium in the second (right) window. Without this change, the window appears far to the right from the last location.

BUG=15199

Review URL: http://codereview.chromium.org/155201
------------------------------------------------------------------------

(No comment was entered for this change.)

 Issue 16185  has been merged into this issue.

 Issue 16347  has been merged into this issue.

 Issue 16283  has been merged into this issue.

Using our 193.0 dev candidate, Official Build 20299, I'm still seeing this issue, 
although to a lesser extent.  

Though the new window is no longer created mostly off screen, it's still not drawn 100% 
on the screen (i.e. about an 1/8th of the screen is off the desktop, or floating on the 
other screen).

Anthony, could you be clearer about "the new window is created"?  What window is being 
created how?

Apologies, happy to clarify, creating a new window using either the context menu or 
"Ctrl+N".

Without knowledge of the behaviour in 193.0, I will say that the original behaviour 
(192) also occurred when opening the app from scratch, and when opening custom 
application windows, as those have there own distinct placement sections.
Cheers,
m.f

laforge: Can you file a different bug with new STR for comment 22?  Especially useful 
will be things like where your existing restored windows are and stuff like that.  The 
main component of this bug is fixed, let's not muddy the waters.

what about  Issue 16088  ?
related to multi monitors and off screen position, except for the Task Manager

 Issue 16088  has been merged into this issue.

Just updated to ..... 

Google Chrome 3.0.193.0 has been released to the Dev channel for Windows.

Highlights in this release:
Fixed  issue 15199  where new windows are opened off screen, in certain conditions, for 
dual monitor users.

(I STILL GET THIS ISSUE - windows 7 x64, dual 1900 x 1200)

andrewdeville,

It's fixed for me on 3.0.193.0. I'm also on windows 7 x64, but I'm dual running 1680 x 
1050.

I am also seeing it fixed.  I am running Windows XP SP3.  I'm not sure if you realize 
it, but the first time you reopen the app after the update it will still be relying on 
the last written placement coordinates, which were incorrect.  After subsequent 
closings, it should behave correctly.
Cheers,

I'm still getting this issue... my version info is:

Chromium	3.0.194.0 (Developer Build 20472)
WebKit	531.5
V8	1.2.13.2
User Agent	Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/531.5 
(KHTML, like Gecko) Chrome/3.0.194.0 Safari/531.5

Still getting it here.
Chrome 3.0.193.0
Win XP Pro SP3
Monitor 2 (primary) = 1600x1200
Monitor 1 = 1280x1024

I got this error after installing the new version (I was sure to close all instances
to allow the update), but later it appears that it has "fixed" itself.
Still, though it was worth adding the comment.

Chrome 3.0.193.0
Windows XP Pro SP3
Monitor 2 = 1680x1050
Monitor 1 (Main) = 1280x800

farore (and others): you might have just experienced what I mentioned above.  The
first time you re-open chrome after updating, it will still be relying on the
incorrect placement values.  So the first startup will be positioned incorrectly. 
After you close all sessions again, the new values written for placement should be
accurate.

michael:

I tried opening several times, the issue still exists.

You have to move the incorrectly-placed window to a correct position, or close it.  It 
won't magically move itself once it's gone wrong.

Okay I'm able to see the fix working now.

I would like to recommend that you force the appropriate persisted data to be cleared 
so that the changes are immediately visible. Keeping the previous, corrupted values 
gives people the initial impression that the issue has not been resolved.

Thanks for the fix!

This appears to be regressed again on ToT, 3.0.196.0 (Developer Build 21216).  This fix 
is required for the next beta release this Friday, please also include a test.

I cannot reproduce this with ToT as of 2009-07-22.
I haven't touched relevant part of Chrome code since the last fix.

(No comment was entered for this change.)

On a dual monitor configuration, using ToT 3.0.196.0 (Developer Build 21216).  

If the browser is in full screen mode on the right hand screen and you open a new 
window (Ctrl+N), the window will open off screen just as before in the original bug.  

In my environment, "About Chromium" shows 3.0.196.0 (21261)
So we should be seeing the same version.

I observed the following:
1. Open a Chrome window and move it to the second monitor.
2. Maximize the window. The window fills the second monitor.
3. Hit CTRL-N.
4. A new window appears slightly right and below the position
   where the original window was at before maximization.

I guess this is the expected behavior?

If this is not, I'd propose filing a new bug for this
because the issue is not very consistent with the Summary line.

The inconsistent behavior is strange.  In the repro case I mentioned, the tab appears 
fully (90%) off screen for me, not just slightly to the right (on XP).  Looking at the 
changes to that file, post your revision on the 9th, the only other revisions change 
from Ben and would not have affected window positioning.  If you could please re-check 
that logic, I'd like to avoid shipping a beta build with that behavior.

I've examined the code but found nothing suspicious.

I've tried more than dozen times to reproduce the reported
behavior, including other monitor configurations (primary right/secondary left,
primary top/secondary bottom, etc) but was unable to reproduce it.

One difference is that I'm using Vista 64 bit.

Can you elaborate on how you can reproduce it?
Especially, can you reproduce it after you move
the window to an ordinary place and close it, and
restart it?

What happens if you hit CTRL-N multiple times?
Does the third window appear at the expected location,
i.e., closely to the second one?

Yuzo

For what it's worth, I can't reproduce the bug with the new test case for this as 
described in comment 40. The behavior I am seeing is consistent with comment 41. I, 
however, am running 3.0.195.1 on windows 7 x64.

I can still repro this issue on a dual monitor setup.
1. Open chrome and position the window on your non-primary monitor
2. Close chrome
3. disconnect secondary monitor
4. Launch chrome

Expected: chrome window launches on visible (primary) monitor)

Actual: Chrome window launches off screen.

(No comment was entered for this change.)

HI, Brian,
That is a different bug. The decision to make the resizing/repositioning
less aggressive , i.e. just guarantee the minimum area (30px x 30px) is shown,
was made at http://crbug.com/9587
Please discuss with pkasting about the decision and file a new bug if appropriate.

Everyone,
I'll close this  bug, because the main issue has been solved.
Please file a separate bug if needed.

Yuzo

another suggestion:
 Issue 16649 
basically, IE and FF do not save windows position if that position is out of the screen even partly