Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

Firefox Nightly Metro version doesn't show the touch keyboard

  • 1 답장
  • 35 이 문제를 만남
  • 10 보기
  • 최종 답변자: philipp

more options

Windows 8: I have installed Firefox Nightly. I have set it as the default browser and consequently, I can use the Metro/touch version of the browser. The problem I have however is that the touch keyboard won't show in the browser. So I can't type in any urls or fill in any boxes, etc. The touch keyboard works just fine in all other applications. I can force it come up by swiping in from the right and pulling up the touch keyboard, but after typing in a link, it disappears again and I have to force it to come up again. That's not appropriate behavior for a touch keyboard.

I have a Surface Pro, and yes, I have removed the TypeCover keyboard and tried to get the touch keyboard to come up but it doesn't.

Any help is appreciated! I much, much, much prefer Firefox over IE and even Chrome!

Windows 8: I have installed Firefox Nightly. I have set it as the default browser and consequently, I can use the Metro/touch version of the browser. The problem I have however is that the touch keyboard won't show in the browser. So I can't type in any urls or fill in any boxes, etc. The touch keyboard works just fine in all other applications. I can force it come up by swiping in from the right and pulling up the touch keyboard, but after typing in a link, it disappears again and I have to force it to come up again. That's not appropriate behavior for a touch keyboard. I have a Surface Pro, and yes, I have removed the TypeCover keyboard and tried to get the touch keyboard to come up but it doesn't. Any help is appreciated! I much, much, much prefer Firefox over IE and even Chrome!

모든 댓글 (1)

more options

hello, thanks for reporting the issue - that is currently a genuine bug in the nightly version, after all that's an unstable preview channel primarily targeted to developers. the problem is dealt with in bug #903866 (please don't post in bug reports - you could vote on bugs instead to show your support).