362403 - showPopup does not work as documented

Status: RESOLVED FIXED

(Toolkit :: UI Widgets, defect)

Description

[daniel newton]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0

At http://developer.mozilla.org/en/docs/XUL:Method:showPopup it is specified that a popup can be positioned using screen coordinates (parameters x & y), however the  popup is only positioned correctly when the element parameter is "document.documentElement".

This bug occurs on trunk (moz 1.9a) and Firefox 2 (moz 1.81)

Reproducible: Always

Actual Results:  
Popup is positioned at 0,0 relative to the document

Expected Results:  
Popup is positioned at x,y in screen coordinates.

Comment 1

[daniel newton]

Attachment: Testcase

Comment 2

[Stephanie Daugherty [:sdaugherty]]

Has simplified testcase, and the behavior seen does appear to go against the documentation, confirming.

Comment 3

[Neil Deakin]

Not necessary to fix this bug once 279703 is done. It adds an openPopupAtScreen method.

Comment 4

[Ondrej Brablc]

In AllPeers we have a dynamic menu in the navigator on the left, that is opened oncontextmenu event by building the menu and calling showPopup().

The code we used was this:

    var menuElement = document.getElementById("apFileBoxContextMenu");
    menuElement.showPopup(aEvent.target, aEvent.screenX, aEvent.screenY, "context", null, null);

However, after a right click in the main browser window (default browser context menu), second call to the same menu misplaced the popup.

The problem has been solved by changing the code to:

    var parent = document.getElementById("apNavigatorPanel");
    document.popupNode = parent;
    menuElement.showPopup(parent, aEvent.clientX, aEvent.clientY, "context", null, null);

Would be nice to have this fixed, it takes some hours to figure this out, I was testing this with Bon Echo 2.0.0.1.

Comment 5

[Ondrej Brablc]

Oops, it looks I should have written this to bug #287357. Aren't those two duplicates?

Comment 6

[Neil Deakin]

Should now be fixed with bug 279703.