搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

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.