Open Bug 423791 Opened 16 years ago Updated 2 years ago

XUL panel.moveTo() not working

Categories

(Core :: XUL, defect)

x86
Windows XP
defect

Tracking

()

UNCONFIRMED

People

(Reporter: zzhumphreyt, Unassigned)

Details

Attachments

(1 file)

User-Agent:       Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; Maxthon; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; .NET CLR 3.0.04506.648)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b4) Gecko/2008030714 Firefox/3.0b4

With XUL, if I open a panel and then immediately move it with the moveTo() method nothing happens, it stays at the position I opened it at.

I've attached a sample extension that demonstrates the issue. Once installed press the 'a' key to make a panel appear at the upper left corner of the screen. It actually should immediately move to point 100, 200.

Reproducible: Always

Steps to Reproduce:
1. Open a panel.
2. Call the moveTo() method to move it somewhere else

Actual Results:  
The panel doesn't move.

Expected Results:  
The panel to move.
Attachment #310399 - Attachment mime type: application/x-zip-compressed → application/x-xpinstall
Component: General → XP Toolkit/Widgets: XUL
Product: Firefox → Core
QA Contact: general → xptoolkit.xul
Flags: blocking1.9?
You should wait until the popup has opened before moving it.

Why aren't you just passing the coordinates to openPopupAtScreen?
Not blocking -- workaround in bug, no rationale given for nomination.
Flags: blocking1.9? → blocking1.9-
I can't determine the coordinates of the popup until it has opened. It's contents will be dynamic and I want to vary its position on-screen based on its size. In Firefox 2 I could open a popup off-screen, determine its size and do calculations based on that, and then call showPopup() again to basically move it. How can I do something similar in Firefox 3?

Since Firefox 3 forces all popups to appear on-screen there's a nasty visual jarring when I move it to its final position.
Mike, could you clarify what the workaround is in answer to comment #4?
Mike, could you clarify what the workaround is in answer to comment #4?
Flags: wanted1.9.1?
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: xptoolkit.xul → xptoolkit.widgets
Flags: wanted1.9.1? → wanted1.9.1+
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: