Steps to reproduce: 1. Open a maximized browser window. 2. Open a link in a new window (ctrl+click, middle-click, window.open(), etc). 3. Un-maximize (restore) both windows. Result: windows are the same size and directly on top of one another. Expected: windows are the same size and in different places.
Assignee: pchen → danm
Component: XP Apps → XP Toolkit/Widgets
QA Contact: sairuh
I'd expect that behaviour, come to think of it. Not that don't think the suggested behaviour would be better. The cascading code won't detect the restored position of its sibling windows; it pays attention only to their current positions. So a newly opened window won't realize it will collide with another window once that window has been restored. The cascading code should probably pay attention only to the restored size, not the current size. And it wouldn't be that hard to do. But this comes under the heading of 800 grit polish; futured for now.
OK, who's the brainiac here? Maximised windows are not supposed to cascade! There's a bug in the bug report! Actually, it's more complex than that, but for most applications, that's exactly how it works. 'Maximised' does not have to mean 'the entire screen', but if it does, the windows so created cannot move or be cascaded, emphatically 'no'.
Jesse meant that the normal/restored position of a window created maximized wasn't cascaded (#3 in the steps to reproduce). It should be.
You need to log in before you can comment on or make changes to this bug.