Not intentional if it's happening due to tab visibility. Are you sure you didn't have the browser scrolled up at all? When you're not scrolled to the bottom (and auto-scrolling doesn't happen) we keep all the messages around until you scroll back down. My hunch would be that you were scrolled up slightly, so it was keeping everything. Don't really see how that would happen with the code otherwise, as we simply count the number of lis in the messages list, and don't do anything based off tab visibility there.

I've experienced this too - in old and new meatspac. Maybe we could use the PageVisiblity api to keep track of new messages for favicon / title of background tabs but not insert them in the document

I think there's a 3-line fix that should take place anytime after the chat is appended.

if (document.hidden) {
  video.stop();
}

Currently there is a page visibility change event listener that starts and stops videos, but chats that are being added while tabbed away are playing (at least the ones "in view") are playing. I'm busy right now but can send this PR tonight if nobody else gets to it by then.

Good find Caleb, that makes more sense to me :) That wouldn't result in it not obeying the chat limit, but could result in it having 30 videos playing, which would never happen if the tab were visible. Awesome!

Let this be a lesson to you all: never stop looking at meatspace.

This could potentially break stiching though : (

That bridge was crossed when we started pausing offscreen videos

I was unaware that was being done… alas our cpus are worth more than our stitch=

I implemented @imakewebthings suggestion, but it appeared that if you were scrolled to the bottom, then new videos would be paused when you return to the window. He mentioned one might need to add a call to Waypoints.refreshAll() during the changeVisibility event callback in main.js, I haven't had a chance to test this though YMMV

Seems like it shouldn't be necessary, unless the videos aren't getting marked as .in-view while the window is minimized (possible). Worth a try though

@byronhulcher I can't reproduce that pausing behavior using the three-liner alone. I'll submit the PR and let others see if they run into it.

Weird, I'm not able to replicate on my MB this morning.