Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Avatar for Username

Vyhľadajte odpoveď

Vyhnite sa podvodom s podporou. Nikdy vás nebudeme žiadať, aby ste zavolali alebo poslali SMS na telefónne číslo alebo zdieľali osobné informácie. Nahláste prosím podozrivú aktivitu použitím voľby “Nahlásiť zneužitie”.

Ďalšie informácie

Táto téma bola archivovaná. Ak potrebujete pomôcť, založte prosím novú otázku.

Firefox 4 stops opening new windows after browser window dragged to second display

  • 1 odpoveď
  • 35 má tento problém
  • 4 zobrazenia
  • Posledná odpoveď od hefela

hefela
hefela
more options

Firefox 4 stops opening new windows after browser window dragged to second display. It's weird. Behavior is fine until I drag any browser window to the attached second display, and after this point it stops opening new windows but will still open new tabs in the same window. Restart fixes it until I drag the window back to the second display.

"Show all bookmarks" stops working too--won't open a new window.

This is after clean reinstall with total deletion of any Firefox/Mozilla folders and the previously installed app and a restart of the computer.

Mac OS X 10.6.7 Firefox 4

Firefox 4 stops opening new windows after browser window dragged to second display. It's weird. Behavior is fine until I drag any browser window to the attached second display, and after this point it stops opening new windows but will still open new tabs in the same window. Restart fixes it until I drag the window back to the second display. "Show all bookmarks" stops working too--won't open a new window. This is after clean reinstall with total deletion of any Firefox/Mozilla folders and the previously installed app and a restart of the computer. Mac OS X 10.6.7 Firefox 4

Všetky odpovede (1)

hefela
hefela Autor otázky
more options

Pretty sure this is either:

Bug 644733

or

Bug 609405

(...and they may be reporting the same thing.)