搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

Learn More

Webpage opened on one sceen not displayed properly when moved to the other screen

  • 3 回覆
  • 3 有這個問題
  • 10 次檢視
  • 最近回覆由 njarif

more options

Setup: imac 5K Retina with a secondary LCD screen attached via thunderbolt-HDMI interface

Two problems were noted after Firefox updated version 38.0.5: 1. Problem #1: When I open webpage on imac (primary screen), it opens OK, then if I move it to the secondary screen it does not display properly. Looks like a second copy of the same page 1/4 size of the original is superimposed on the upper left corner. See Attached screen shot #1

2. Problem #2: When I Open a webpage on the secondary screen, it opens ok (see #2 sceen shot) , then if I move it to the primary screen (imac), it is not displayed properly. Looks like the page is displayed on the primary zoomed in. See attached screen shot #2 (on secondary screen) and #3 after being moved to the primary screen (imac)

Setup: imac 5K Retina with a secondary LCD screen attached via thunderbolt-HDMI interface Two problems were noted after Firefox updated version 38.0.5: 1. Problem #1: When I open webpage on imac (primary screen), it opens OK, then if I move it to the secondary screen it does not display properly. Looks like a second copy of the same page 1/4 size of the original is superimposed on the upper left corner. See Attached screen shot #1 2. Problem #2: When I Open a webpage on the secondary screen, it opens ok (see #2 sceen shot) , then if I move it to the primary screen (imac), it is not displayed properly. Looks like the page is displayed on the primary zoomed in. See attached screen shot #2 (on secondary screen) and #3 after being moved to the primary screen (imac)
附加的畫面擷圖

由 njarif 於 修改

被選擇的解決方法

Hi njarif, I have seen this before and could never describe it correctly. I think you have enough information here to file a bug:

從原來的回覆中察看解決方案 👍 1

所有回覆 (3)

more options

選擇的解決方法

Hi njarif, I have seen this before and could never describe it correctly. I think you have enough information here to file a bug:

more options

Bug number 1218028

more options

The issue has been resolved in Firefox v 42.0