搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

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

  • 3 个回答
  • 3 人有此问题
  • 7 次查看
  • 最后回复者为 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