Closed Bug 265811 Opened 20 years ago Closed 20 years ago

pop-up UI elements (listboxes, context menus) not displaying

Categories

(Core :: XUL, defect)

PowerPC
macOS
defect
Not set
major

Tracking

()

RESOLVED DUPLICATE of bug 264235

People

(Reporter: richardgodbee, Assigned: jag+mozilla)

References

Details

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en) AppleWebKit/125.5 (KHTML, like Gecko) Safari/125.9
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a5) Gecko/20041023

On the 2004102306 Mac OS X trunk build (www.mozilla.org -> Developers -> Nightly Builds), drop-
down listboxes do not work.  When you click a listbox, the list of choices does not appear.  However, 
you can click in the area where the choices should appear and select the choice that would normally 
appear where you clicked.

Reproducible: Always
Steps to Reproduce:
Click a drop-down listbox.  This can be the Back or Foward button's listbox, a <SELECT> element 
on a Web page, or any of the drop-down listboxes in the Prefences dialog.
Actual Results:  
No drop-down list of choices is displayed.

Expected Results:  
Drop-down list of choices is displayed.

I checked the 1.7.3 OS X release as well as the 2004102306 Linux build, and neither exhibit this 
problem.  (I delete my Mozilla profile when changing builds.)  Both the Modern and Classic themes on 
OS X have this problem.
After more playing, it appears this problem is more than just listboxes -- right-clicking the page, a 
link, an image, etc. doesn't display the context menu.  The menus on the menubar *do* work.  (Sorry 
for the bugspam.)
Summary: drop-down listboxes do not display, but you can still select items → pop-up UI elements (listboxes, context menus) not displaying
Please retest with today's build.  This should have been fixed yesterday
afternoon by the patch for bug 264235.
Depends on: 264235

*** This bug has been marked as a duplicate of 264235 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.