GitLab

Without this, we can get some cases where a non-remove display change
can get some persistent bounds stored and won't get overwritten when
a remove display change happens.

Introduce a mechanism where persistent bounds are calculated when a
display change signal is received, but not written to the window
state unless a remove signal is received.

Test: manual, added tests
Bug: 1115675
Change-Id: Id3b642d5912510c451e78a0f9227437d1ce2de1b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2353065Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
Commit-Queue: Sammie Quon <sammiequon@chromium.org>
Cr-Commit-Position: refs/heads/master@{#797895}