Mozilla 도움말 검색

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

자세히 살펴보기

Twitter DM screen doesn't automatically update when receiving new DM?

  • 1 답장
  • 2 이 문제를 만남
  • 11 보기
  • 최종 답변자: guigs

more options

Hi,

I'm using Firefox 33.1.1. If I try and have a conversation via direct messages on Twitter, when I received a new DM, the screen doesn't automatically update to show the new message at the bottom of the conversation window. When I send a message to the other person, the screen does update and my message appears at the bottom, so this issue only happens when people send DMs to me. I see the notification pop-up in the bottom-right of the screen showing that I've got a new DM, but it doesn't appear in the DM window and I have to refresh the page manually every time. It's quite annoying.

I've tried restarting Firefox in Safe Mode, so no add-ons or running, and the issue persists.

Any idea what's causing it? Is it a compatibility issue with Firefox?

Thanks!

Hi, I'm using Firefox 33.1.1. If I try and have a conversation via direct messages on Twitter, when I received a new DM, the screen doesn't automatically update to show the new message at the bottom of the conversation window. When I send a message to the other person, the screen does update and my message appears at the bottom, so this issue only happens when people send DMs to me. I see the notification pop-up in the bottom-right of the screen showing that I've got a new DM, but it doesn't appear in the DM window and I have to refresh the page manually every time. It's quite annoying. I've tried restarting Firefox in Safe Mode, so no add-ons or running, and the issue persists. Any idea what's causing it? Is it a compatibility issue with Firefox? Thanks!

모든 댓글 (1)

more options

Potentially this is an issue with Firefox, I would be happy to test. I ran a test between two vms. I messaged myself :-/ but when I switched between the two instances of the message, it did not automatically update until I tried to send a new message. There may be better test cases, but I can confirm the behavior. As for investigation for development, bugzilla.mozilla.org and stackoverflow.com should have the right audience for troubleshooting why.