43743 - Loading with clean profile sets screenX and screenY for main window

Status: VERIFIED DUPLICATE of bug 42345

(Core :: XUL, defect, P3)

Description

[Cesar Eduardo Barros]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.14 i586; en-US; m17) Gecko/20000624
BuildID:    2000062408

Loading 2000062408 after removing the profile set the default window placement
to +2+2 (in localstore.rdf). This makes every window come in the same place in
the screen.

Reproducible: Didn't try
Steps to Reproduce:
1.Remove the profile
2.Load mozilla

Actual Results:  screenX and screenY for #main-window in localstore.rdf were
both set to 2

Expected Results:  Both should be set to -1

Fixing this ends all main window positioning problems on Linux

Comment 1

[Asa Dotzler [:asa]]

pav, is this something you can take out of Browser General?

Comment 2

[Otto]

I can reproduce this on Red Hat 6.2

user-agent: Mozilla/5.0 (X11; U; Linux 2.2.14-5.0 i686; en-US; m17) Gecko/20000726
build id: 2000072608

Comment 3

[Asa Dotzler [:asa]]

over to toolkit.

Comment 4

[Peter Trudelle]

I don't see this as worth the time/risk for NS6, ->future

Comment 5

[Cesar Eduardo Barros]

Risk? What risk? I can't understand why changing the default from 2 to -1 would
be risky. I do it all the time when I install with a clean profile (which means
every time I reinstall).

Comment 6

[Peter Trudelle]

Sorry, that was a canned phrase - but there is always some risk in any change,
and this one didn't seem worth much.  In any case, I didn't really understand
you just wanted the default changed. Exactly what problems does this fix, and
what else is affected (if anything)?  reassigning to dr

Comment 7

[Cesar Eduardo Barros]

Without both values at -1 (at least last I checked), all windows start fixed at
+2+2; with both at -1 (which was the default before the random-messy-nutty
resizing bugfest about a month ago) it lets enlightenment decide where to put
its windows. Since during the bugfest I had played with the setting, I spotted
the strange new default. By changing them by hand from 2 to -1 after installing,
I make it behave as it was before the bugfest.

Comment 8

[Dan Rosen]

I am running RedHat 6.2, but am using the sawfish WM. When I follow your steps
to reproduce, I get +9+9. This is because Mozilla is trying to remember its
position, and sawfish places it at +9+9 (according to the browser) by default. A
possibility for the future would be to add a checkbox somewhere in preferences
to allow for tweaking of window positioning, that is, whether it remembers its
own position or lets the window manager do it itself. It's a fairly trivial task
to add that sort of code, but it bears some discussion regarding platform
parity. Marking WORKSFORME, since the code is perfectly functional, and since
you can set enlightenment to override just about anything anyway. If it still
bothers you a lot, you could investigate who made the change (using lxr) and
why.

Comment 9

[Cesar Eduardo Barros]

Yeah, lately I've been getting +9+9 too. But it's gotten worse.

I have now 2000080808, which instead of treating -1 as "let the window manager
position the window", changes it to +8+8. On first time loading I still get +9+9.

All these values are bogus; Enlightenment, if left alone (as happened in
2000080208 and before by editing the saved X and Y position to -1), not only was
allowed to dynamically reposition the child windows (instead of making them all
appear at the same spot in the screen), but also never used +8+8 or +9+9 as the
initial position for the first window. It (in my normal almost-empty desktop)
always uses +16+0. So, it's not remembering his window position; it's inventing one.

This is extremly annoying, since it forces _all_ child windows to the same spot,
making it harder to find them without tabbing with the keyboard. If I understood
the code, I would already be downloading it and finding the bug; but I have no
clue as to where should I look at.

Also, there's no way in E to force a dynamic window position; only to force a
fixed one (which is disabled btw; I only force a 800x600 size on the first window).

Comment 10

[Dan Rosen]

better still, dup of bug 42345

Comment 11

[Dan Rosen]

*** This bug has been marked as a duplicate of 42345 ***

Comment 12

[Scott Brodmerkle]

Verified dupe.