User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8a5) Gecko/20041010 Firefox/0.9.1+ Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8a5) Gecko/20041012 Firefox/0.9.1+ I have two monitors situated next to each other. The left one is set as the "primary display", the right as the "secondary". With FF open on the secondary display - whether FF is open on the primary display or not - clicking any toolbar item (File, Edit, etc.) causes the respective dropdown menu and any tooltips to appear only on the primary monitor. It also makes no difference how many tabs are open on either monitor. Reproducible: Always Steps to Reproduce: 1. The behavior depends on FF operating on secondary display whether FF is open on primary display not. 2. It makes no difference whether you open FF on primary display and slide to secondary or open it directly on secondary display. (Unlike bug 138933, it doesn't matter when you do this. 3. Click any toolbar menu item or a bookmark from the Personal Toolbar that contains a list of several individual bookmarks. Actual Results: Dropdown menu and tooltips appear (only) on primary display. Expected Results: Open menus and tooltips on secondary display. This appears related to bugs 138933, 255551, 259417, and 260448, but the behavior doesn't matter how you open Firefox, which display you start first, etc., and it happens no matter how you start FF. Also, on my system (Matrox G550 / dual dvi / 2 tft displays) it only began with the Trunk build of 12 Oct 04. Prior to that I had put in a new trunk build (zip) daily using the same profile for at least three months. This behavior never appeared before. I've just gone back to the trunk build from 10 Oct, and the behavior disappeared. I have not changed the profile in any of the test cases. I'm quite sure it's a Trunk-only problem because this afternoon I tested last night's (12 Oct 04) official Branch build, and it worked fine, i.e., the drop-down menus and tooltips appeared on the secondary monitor as they should have. I've also replicated the problem with today's trunk build using a completely new "installation" and a completely new profile. I've been using my setup for months, and I'm 100% sure this behavior only started yesterday (12 Oct). As mentioned above, I've now gone back to the nightly trunk of 10 Oct. - using same profile - and everything is fine.

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

Phil, reporter clearly said the behavior only started on Oct 12. How could that be a dup of bug 98830? Please don't lump regressions with long-standing issues.

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