mirror of
https://github.com/zulip/zulip.git
synced 2025-11-03 21:43:21 +00:00
8d33a62eca
It should be very rare to discover new unread messages during a message_fetch call. This can potentially happen due to races (fetching just as a new message arrives), but it shouldn't be the common case. Previously, we would trigger a full rerender of all UI displaying unread messages every time a bulk message fetch operation returned (including every time one narrowed), regardless of whether any actual state had changed. Fix this by actually checking if we discovered any new unread messages.