On phone we use 60% of the screen which is huge on
tablet. This change uses 30% of the screen for the
flyout on large screens & enforces a minimum for
that value.
Test: manual - get a long message in a bubble on a
tablet, it should have similar width
as it does on phone.
Bug: 186776550
Change-Id: I500c566edd9941dc2bd149692eaf95c6e6f4aa61
- manage button should be inset from the expanded view edge
but the menu should be flush with expanded view edge.
- button size is smaller (36dp instead of 40dp)
- more padding (16dp above / below on both tablet & phone)
- diff colour N1-800 instead of N1-900
Test: visual 1 - expand a bubble and look at 'manage' button
2 - tap on the button and look at the menu
3 - do 1 & 2 on tablet & in RTL & on phone
landscape
Bug: 183658858
Change-Id: I4b5ffc26602b72ee28d26476fc222df3e2e1e80b
The 2 cases when a fullscreen activity is launching with starting
window (step a), and it launches embedded activity before it is
drawn (step b): (assume X,Y are 2 different activities)
1. a. Task - X (Fullscreen) - starting window
b. Task - TaskFragment - X (Left side)
- TaskFragment - Y (Right side) - starting window
2. a. Task - X (Fullscreen) - starting window
b. Task - TaskFragment X (Left side)
- TaskFragment - Task - Y (Right side) - starting window
The starting window will be transferred to the top activity (so it
won't be covered by other embedded activity according to z-order)
of the base task with keeping the configuration of base task.
Another case is to bring the base task to front with snapshot
starting window. That will find all visible activities and share
the starting data to them. Then the starting window can be removed
until all visible embedded activities are drawn.
Bug: 189385912
Test: ActivityRecordTests#testStartingWindowInTaskFragment
Change-Id: Ia4c0f4142d49f9e6ac9c39980b1157c35069ec4e
Dependency.get calls from BatteryMeterView to this controller.
BatteryMeterView is used in QuickStatusBarHeader, KeyguardStatusBarView,
PhoneStatusBarView, and SplitShadeHeaderController, so
BatteryMeterViewController is added to the
controllers for those views.
Bug: 138786270
Test: atest and manual
Change-Id: I4d23a32d4ecda4f4327552b3703e9893ad544bdb
Merged-In: I4d23a32d4ecda4f4327552b3703e9893ad544bdb
Keep new test changes isolated to the new test to avoid disruption
to the existing tests
Fixes: 195101353
Test: atest KeyguardViewMediatorTest
Change-Id: Ia7706ce8b3923c1bf4fccd3f15edf97c60893472
When switching tasks from the task has IME shown to another task
without showing IME (e.g. youtube apps.), the flickering might happen
because the next activity accidentally received the IME insets attached
in the previous activity.
If the IME is attached to one app window on that time, even the next
app window is behind the IME window, conceptually the window should
not receive the IME insets if the next window is not eligible IME
requester and ready to show IME on top of it.
Fix the logic in InsetsPolicy#adjustVisibilityForIme for the above
case.
Fix: 192337037
Bug: 194746204
Test: atest WindowStateTests#\
testAdjustImeInsetsVisibilityWhenTaskSwitchIsAnimating
Merged-In: Ib3a1eacedd3763bcf1e6eed82e7efdf01c50b204
Change-Id: Ib3a1eacedd3763bcf1e6eed82e7efdf01c50b204
(cherry picked from commit f4eb054460)
Activity#onCreate is called before receiving the TaskFragment
appeared event in the client process. So, the client split
controller created another split and resulted in unexpected
behaviors.
Bug: 194860679
Test: start activity to side
Test: wm presubmit
Change-Id: Iac34bd39376940c5c0224c8687ad9858a4190e20
