搜尋 Mozilla 技術支援網站

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

Learn More

Bug? Firefox, Silverlight and big resolutions

  • 3 回覆
  • 6 有這個問題
  • 8 次檢視
  • 最近回覆由 guigs

more options

Hi,

We are a company with Firefox 24 deployed to more than 2000 PCs. We have an Intranet app made with Silverlight working ok with this Firefox version. But now we want to update to Firefox 33 and testing it we've found that it doesn't work with the Silverlight app with big monitors. It seems to be related to the resolution of the monitor, or at least, to the size of the Firefox window. The problem is that the mouse pointer doesn't seem to be pointing where it is. It's better explained in this screencast, where you can see that in a 1024px Firefox window it works OK, but when it's 1920px it doesn't work: https://www.youtube.com/watch?v=DA9DLYc-vpE

We tried different versions of Silverlight, currently 5.1.30514.0 I don't know in which Firefox version it started to appear this bug. With Internet Explorer it works.

Any idea?

Hi, We are a company with Firefox 24 deployed to more than 2000 PCs. We have an Intranet app made with Silverlight working ok with this Firefox version. But now we want to update to Firefox 33 and testing it we've found that it doesn't work with the Silverlight app with big monitors. It seems to be related to the resolution of the monitor, or at least, to the size of the Firefox window. The problem is that the mouse pointer doesn't seem to be pointing where it is. It's better explained in this screencast, where you can see that in a 1024px Firefox window it works OK, but when it's 1920px it doesn't work: https://www.youtube.com/watch?v=DA9DLYc-vpE We tried different versions of Silverlight, currently 5.1.30514.0 I don't know in which Firefox version it started to appear this bug. With Internet Explorer it works. Any idea?

所有回覆 (3)

more options

I've called the big guys to help you. Good luck.

more options

選擇的解決方法

more options

Dimas it looks like Gijs is helping you in the bug, I will mark the bug as the solution for now, however if there are more questions or support needed, please feel free to respond to this post and we are happy to help.