Propagate configuration change into QSFragmentCompose view
For some reason some configuration changes are not properly being passed into the NotificationShadeWindowView after a particular sequence of events: 1. Increase font size 2. Increase display size 3. Decrease font size 4. Decrease display size This causes the compose view to not have the most up to date configuration and showing wrong state. Instead, propagate the configuration change on the fragment that is sent from FragmentHostManager into the view (bypass the view hierarchy). This would cause, at worst, a double call to configuration changes in the ComposeView, but it should be deduplicated as the config value is the same. Test: manual, perform steps and open shade Bug: 429355827 Flag: EXEMPT bug fix Change-Id: I9afeb9eee2b511a8d0e68cd2a8eaa2637a949360
Loading
Please register or sign in to comment