Open Bug 237833 Opened 20 years ago Updated 2 years ago

"Opening" dialog insists on placing itself in alert position (centered), but is not auto-placing

Categories

(Toolkit :: Downloads API, defect)

x86
Linux
defect

Tracking

()

People

(Reporter: bzbarsky, Unassigned)

Details

BUILD: Firefox 0.8 on Linux

STEPS TO REPRODUCE:

1) Point firefox to a file it doesn't know how to handle (I used a .ps file)
2) When your WM asks you to place the resulting window, place it

EXPECTED RESULTS:  The window appears where you placed it

ACTUAL RESULTS:  The window briefly flickers where you placed it and then jumps
over to be centered on top of the Firefox browser window ("alert position").

Windows moving about of their own accord is extremely disconcerting.

Note that I'm fine with it placing itself in alert position, but then it
shouldn't ask the WM to be placed first.  It should just place itself.  That's
what the SeaMonkey helper app dialog does, and also what actual alerts do.
This probably occurs only with GTK2+XFT builds, and not GTK1 builds.
Yeah, I'm just using the build linked off Mozilla.org, which is a GTK2-XFT
build.  Why would this depend on the toolkit, though?
And if this _is_ toolkit-dependent, blizzard should know...
(In reply to comment #2)
> Yeah, I'm just using the build linked off Mozilla.org, which is a GTK2-XFT
> build.  Why would this depend on the toolkit, though?

I'm assuming that since the bug is so similar to bug 237832, which I tested and
only occurs on GTK2+Xft (not GTK1), this one probably does too, which is why I
said probably. I'm not using a WM that asks me to place the window, so I haven't
been able to test this one (though I tested bug 237832).
P3, 1.0b
Status: NEW → ASSIGNED
Priority: -- → P3
Target Milestone: --- → Firefox1.0beta
Assignee: bugs → nobody
Status: ASSIGNED → NEW
Priority: P3 → --
QA Contact: aebrahim-bmo-507 → download.manager
Target Milestone: Firefox1.0beta → ---
Flags: blocking-firefox2?
From what I'm seeing here, this seems like something edge-to-cornerish, based on WM.  Certainly would consider a patch, but not going to block on this.
Flags: blocking-firefox2? → blocking-firefox2-
Not much to do with the WM, everything to do with the moveToAlertPosition() calls in the Firefox UI here.
Product: Firefox → Toolkit
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.