X
點擊此處開啟此網站的行動版。

技術支援討論區

Windows 10 Technical Preview 10041, Firefox Nightly x64 most current, can launch, can't access settings, cannot place cursor in URL box

已張貼

Have Windows 10 Technical Preview build 10041, Firefox Nightly x64 39.0a1 most current. Firefox will launch, but when browser appears no input to screen possible. Can't access settings, can't place cursor in URL box. Tried compatibility modes with no success. I may not have used this browser on Thursday, March 26, but it was working without issue on Wednesday, March 25. My speculation would be that one of the last two nightly updates broke this. This question posted from Chrome as Firefox not operating.

Have Windows 10 Technical Preview build 10041, Firefox Nightly x64 39.0a1 most current. Firefox will launch, but when browser appears no input to screen possible. Can't access settings, can't place cursor in URL box. Tried compatibility modes with no success. I may not have used this browser on Thursday, March 26, but it was working without issue on Wednesday, March 25. My speculation would be that one of the last two nightly updates broke this. This question posted from Chrome as Firefox not operating.

被選擇的解決方法

hello, that appears to be a known bug that's being worked on (bug #1147953). please also note that as long as windows 10 is in it's pre-release preview state and there are still changes to the core platform, it will not be fully supported by firefox and things are bound to go wrong on occasion.

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

額外的系統細節

應用程式

  • User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2343.5 Safari/537.36

更多資訊

philipp
  • Top 25 Contributor
  • Moderator
5304 個解決方法 23419 個答案

選擇的解決方法

hello, that appears to be a known bug that's being worked on (bug #1147953). please also note that as long as windows 10 is in it's pre-release preview state and there are still changes to the core platform, it will not be fully supported by firefox and things are bound to go wrong on occasion.

hello, that appears to be a known bug that's being worked on ([https://bugzilla.mozilla.org/show_bug.cgi?id=1147953 bug #1147953]). please also note that as long as windows 10 is in it's pre-release preview state and there are still changes to the core platform, it will not be fully supported by firefox and things are bound to go wrong on occasion.