-
Notifications
You must be signed in to change notification settings - Fork 62
New messages occasionally have paused video #52
Comments
So the bug I'm seeing sounds like what @tec27 but not what @imakewebthings was finding and playing with last night, so possibly two different pause-related bugs? I saw this one at least 10-15 times last night, especially as more and more people were entering meatspace after Clay Shirky's tweets. I got it to happen once in my local machine, too (out of hundreds of times). Here's what I see:
If I can get this to happen again locally I'll try to record a little of what I see... |
@jasonrhodes Ok, this makes sense in the disparity between what I was seeing last night and the ways to resolve this (window resizing, adding chats.) I believe what I ran into was a Chrome-only bug that I've seen on v2 occasionally, which is that videos freeze randomly and enter that As @tec27 mentioned last night, chats are deleted after chats are added. Everything about your report, Jason, sounds like what would happen in that case. I'm more surprised that this isn't happening more often or all the time. While I can't reproduce this reliably with the current code base if you throw a setTimeout of any decent length around the chat removal block... setTimeout(function () {
if (children.length > MAX_LIMIT)
...
}
}, 1000); ...once you get enough chats to where removal happens, you'll see this. If this is enough of a reproduce step, I'll send a PR to add the refresh after removal. |
Sounds pretty likely to me, @imakewebthings. |
Definitely related to waypoints in some way, but if messages come in in quick succession (seemingly), the last couple messages (maybe more? maybe less?) don't get marked as being in view, or get marked as being in view and then marked as out of view, and so are paused until another message comes in.
I looked at the DOM in Chrome devtools when this occurred and definitely saw the last two videos, despite being visible, did not have the in-view class at the time.
I suspect this is something to do with the videos not being loaded when they're added to the DOM, although I have no real way to prove this easily. Further investigation needed!
The text was updated successfully, but these errors were encountered: