433037 - [Followup] Wrong menupopup positioning inside HTML table

Status: RESOLVED WORKSFORME

(Core :: Layout, defect)

Description

[Chris Pearce [:cpearce (Not reading bugmail)]]

Attachment: Testcase from bug 392160

This bugs is a followup of bug 392160. The checkin for bug 392160 did not fix the original complaint, and we've closed the bug so it gets off the "patch has approval but bug isn't closed" list.

From Bug 392160 comment 1:

<quote>

It seems that positioning of the menulist popup is wrong when this menulist
element is placed inside an HTML table (or element with display:table-cell)
next to a multiline text block. To test, save the testcase and open it as a
dialog using this command:

  window.openDialog("file:///.../popup_positioning.xul", "_blank",
"width=500,height=500,resizable");

Click the dropdown arrow of the menulist - the position of the popup will only
be correct if you resize the dialog to make sure the text doesn't wrap.

Tested in Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a8pre)
Gecko/2007081320 Minefield/3.0a8pre. Firefox 2.0 generally doesn't wrap the
text here so that the testcase doesn't work.
</quote>

Comment 1

[Chris Pearce [:cpearce (Not reading bugmail)]]

Further work to fix the issue originally reported in bug 392160 should be done here.

Comment 2

[Ian Weiner]

Hi, I just wanted to point out that this bug shows up in the Grab and Drag extension version 2.7.4, under Firefox 3.5.4 and Windows Vista, in the XUL-based preferences window. I've worked around the bug there for G&D 2.7.5 by setting align="top" for the controls' parent hbox.

Comment 3

[Elbart]

For modern Firefox-versions, you have to add a new boolean to enable execution of remote XUL from within the console: dom.allow_XUL_XBL_for_file;true

And the bug is still very much alive and can be observed in normal Firefox since the change of the Plugin-state-setting to a menulist, see bug 981125.

Screenshot of current Nightly: http://i.imgur.com/lGLWQl6.png

Comment 4

[Elbart]

And this screencap shows that there are two areas where the mouseover-highlight is being registered: http://i.imgur.com/s1yo2uY.gif

Comment 5

[Neil Deakin]

I believe this was fixed by bug 1130400.

Comment 6

[Neil Deakin]

Let's assume so.