Closed Bug 42536 Opened 25 years ago Closed 25 years ago

Browser has its own (bad) idea of where its windows should get

Categories

(SeaMonkey :: General, defect, P3)

x86
Linux
defect

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 42035

People

(Reporter: cesarb, Assigned: asa)

Details

From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.14 i586; en-US; m16) Gecko/20000614 BuildID: 2000061408 Mozilla has now started ignoring the window manager. Setting the size to a "default" 800x600 (which it thinks I resized it to -- in fact it was E) is good, but ignoring the window manager's set position is evil, since the window manager has a better idea of where to put new windows (it uses the less cluttered place in the desktop by default, while Mozilla choses places where most of the window is outside the desktop). Reproducible: Always Steps to Reproduce: See description Actual Results: See description Expected Results: See description I believe this has something to do with the fact that it windows seem to come up with a small size and then resize to the right size.
dupe of 42522 probably *** This bug has been marked as a duplicate of 42522 ***
Status: UNCONFIRMED → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
The other bug says nothing about ignoring E's window positioning... It does not look like a dupe for me.
read it too quickly, un-duping.
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
I bet it's the same bug (I filed the other one), and indeed I also saw a positioning problem which I hadn't previously been seeing: the mozilla window appeared so high up on the screen that its titlebar was almost entirely behind the kde taskbar, so it would have been difficult to move it. I didn't mention it because I forgot about it (not sure if it happened more than once, or only the first time).
It's actually a dup of this one. Submitter: I'm aware that E allows you to save window sizes and positions; the problem here is that mozilla is resizing *after* it's mapped. You're probably experiencing a midair collision between the E resize and the Mozilla resize. *** This bug has been marked as a duplicate of 42035 ***
Status: UNCONFIRMED → RESOLVED
Closed: 25 years ago25 years ago
Resolution: --- → DUPLICATE
Nope. First, I save size and not position; and E applies the size to the first (main) window only. Second, I can actually see the small 200x200 window open in a corner, it then moves to another part of the screen (so it´s not E; I´ve seen it open in the UL corner lots of times, and E would never place it there -- it´s where I move the first window to) and then after that resizes to its real size. The ¨second¨ window (after move but before resize) often looks like a banner (about the same size).
cesarb@dcc.ufrj.br, do you still see this problem with a new M17 nightly?
Keywords: verifyme
Yes. 2000062108 still has its own stupid idea of where windows should go. I just opened two windows, the first one got the ¨200x200¨ size in +0+0 (exactly over the main window -- E would never put it there) and then resized to 800x600 in the same place, and the second got put exactly to the right of the main window (+800+0 if I understand X´s numbering right) in my 1024x768 desktop. Other programs always get a fixed position (xmms) or the least crowded place in the desktop (the rest).
Downloaded 2000062408 right now. It still has its own idea of where the windows should go, but now its ideas for window placement aren´t that broken anymore (it puts it in Win-like ¨cascade¨ style instead of letting E put them in the crazy random places E likes to put windows), and there´s no ¨magic resizing¨. Not letting the window manager position the windows isn´t very good, but that´s a separate issue (which should get its own bug). You can call this one ¨fixed¨.
gonna verify dup. bryner checked in the fix for 42035 on 6/21, so you wouldn't see it in the 6/21 build but you would in the 6/24.
Status: RESOLVED → VERIFIED
Keywords: verifyme
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.