commit be5a6e5c5107a06c9734f42fe9f033cb3db99b1e
author Caitlin Shkuratov <caitlinshk@google.com> Mon Nov 14 18:53:20 2022 +0000
committer Caitlin Shkuratov <caitlinshk@google.com> Mon Nov 14 19:31:48 2022 +0000
tree 5d50dc065f4c8a2cd9f003e3ac91e2cc21e6ac93
parent 2c34290e8741107ff0f03b4f326da7a14c1675a2

Update ConfigurationController to not store maxBounds by reference.

See bug for more information, but tl;dr is: Since maxBounds was directly
referencing the configuration's bounds, it got updated before
`onConfigurationChanged` was triggered. This meant listeners never got
the `onMaxBoundsChanged` callback, so `PrivacyViewDotController` never
updated its bounds and has the incorrect bounds.

Bug: 245799099
Bug: 256754780
Bug: 259105114
Test: manual: Verify privacy dot shows up correctly in all displays
Test: atest ConfigurationControllerImplTest

Change-Id: Ic3968b89a240f28630eff756ca0a7eaacbf5dee2