diff options
| author | 2023-10-09 11:15:05 +0200 | |
|---|---|---|
| committer | 2023-10-10 11:24:46 +0200 | |
| commit | 131356a85de79b8ec50327dcf1433f61c3785cf0 (patch) | |
| tree | 437bf63088f363422987e34a554bebacdf2ec073 /api/api_test.go | |
| parent | f9a6b1a719772bdda64a11cdc62177dd14352f21 (diff) | |
Fix context and resources used for keyguard presentation
This avoids creating a new context if the default context in the dagger graph is already the correct one for the display in the scope.
Before this cl, a new context was created also for the default display, and it had the wrong android.R.attr.isLightTheme value.
Ideally we should use the DisplaySpecific context in ClockEventController as well, but we first need to fix isLightTheme wrong value in the new display specific context.
Test: Manually check clocks colors + KeyguardClockSwitchScreenshotTest
Bug: 299256162
Change-Id: I942c8e35a644df27a6f442d7eddf8a2a767765be
Diffstat (limited to 'api/api_test.go')
0 files changed, 0 insertions, 0 deletions