Over inside the browser, I'm going to go ahead and give things a refresh, and I'm also going to open up the Developer Tools so we can view our console.log statement. You'll notice on smaller screens the styles remove the sidebar. Now I'm going to hit enter a few times. Obviously, we shouldn't be able to send empty messages but we can for the moment, and you can see that Should scroll is printing:

It's not actually going to scroll because the height of our messages container doesn't actually exceed the height of the browser space given to it, but it does indeed pass the condition. Now as we get down further and messages start to drop off the bottom of the screen, you'll notice the count in front of the message stops going up. The count incremented every time Should scroll printed, but now it stays at 2 even though I'm adding new messages further.

In this case, we can scroll back down to the bottom and add a new message, abc. This should cause the browser to scroll, we're kind of near the bottom. When I do it Should scroll increments to 3, which is fantastic.

If I scroll up to the top of the list and type 123 and hit enter, Should scroll does not increment to 4, which would be correct. We do not want to scroll a user to the bottom if they're up at the very top.