tree f2d274825b956a592e6ab4ab370fbb0bb1517631
parent 6cdc33c81d4c271e68589d204cfc9fee5000823c
author Ben Rohlfs <brohlfs@google.com> 1600323484 +0200
committer Ben Rohlfs <brohlfs@google.com> 1600347836 +0200

Add guards to regular change update polling

We are regularly polling every 10 seconds for change updates. If we
detect a new change message, then we show a toast to the user such that
they know that reloading the change is a good idea.

However, we are showing this toast too often, especially when the user
has just sent a reply themselves. The reason is that we did not have
any checks for the update still being relevant. This change adds two
checks: Is the change page loading? Was the change already updated?

This is most likely not fixing the issue 100%, but we are hoping for
99%. And we have plans for switching away from the polling updates
altogether, so we don't want to invest a huge amount of time into
fixing the remaining 1%.

Bug: Issue 13394
Change-Id: I579bf270c5ab8bca5343bd424a6f0122c8fb17ba