본 사이트는 여러분의 사용자 경험을 개선하기 위해 유지 보수를 진행하는 동안 기능이 제한됩니다. 도움말로 문제가 해결되지 않고 질문을 하고 싶다면 Twitter의 @FirefoxSupport 및 Reddit의 /r/firefox 채널을 활용하세요.

Mozilla 도움말 검색

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

자세히 살펴보기

Issues with facebook in Firefox iOS

  • 1 답장
  • 3 이 문제를 만남
  • 12 보기
  • 최종 답변자: alessio92

more options

I used facebook's desktop site within a browser on my iPad as I don't like having both the facebook app and messenger app installed; plus I find the normal desktop site interface easier to use. For most features this works ok, but I find that when I tag someone in a comment and then hit enter to post the comment, Firefox for iOS starts a new line rather than posting the comment. This also occasionally happens with normal comments where I haven't tagged someone. As there's no longer a 'Post' button on Facebook, it simply means I can't add my comments on. It's driving me mad. This issue does not occur in Safari and has been a problem for a number of months. I'd hoped the recent heavy overhaul of FF would help but it hasn't changed anything.

Does anyone know how to resolve this?

I used facebook's desktop site within a browser on my iPad as I don't like having both the facebook app and messenger app installed; plus I find the normal desktop site interface easier to use. For most features this works ok, but I find that when I tag someone in a comment and then hit enter to post the comment, Firefox for iOS starts a new line rather than posting the comment. This also occasionally happens with normal comments where I haven't tagged someone. As there's no longer a 'Post' button on Facebook, it simply means I can't add my comments on. It's driving me mad. This issue does not occur in Safari and has been a problem for a number of months. I'd hoped the recent heavy overhaul of FF would help but it hasn't changed anything. Does anyone know how to resolve this?

글쓴이 alessio92 수정일시

모든 댓글 (1)

more options

Please can someone tell me if there's any way I can report this directly to Mozilla as a bug rather than posting on the forum?