Making it visible to accessibility even when it’s completely hidden
behind a task. I had to mark it visible as a view. Now it’s invisible
only when there are no tasks in RecensView, to hide it from
accessibility.
Focusing on the button completely reveals it.
Bug: 72222505
Test: Manual
Change-Id: Ia31a1136e07faed93b4a44d5be69483d3b88364d
When in portrait mode with nav bar on the right , we need the right
inset to be applied to the layout.
Bug: 72222505
Test: Manual
Change-Id: I06ac864097fb3cfb833de3e40921be4e19eb5f54
It’s an initial implementation, i.e. no fancy effects.
It shares a parent (LauncherRecentsViewContainer) with RecentsView.
The button is centered in clear_all_button_container, which gets
positioned programmatically to the right of the last task. (RTL polish
will be a separate CL as well).
Bug: 72222505
Change-Id: Ia912908a93a30c2f51450ccf0f97c7495e7916d5
Test: Manual
The list is:
Close [task]
<items from the task’s popup menu>
Also making a current task in carousel get accessibility focus. This
prevents losing focus after closing a task, and makes sense generally.
Bug: 72409756
Test: Manual
Change-Id: I2cfdfd4693a255f63417d922cb6aa4841db1d3c3
> Wallpaper based theme support
> Light/dark system UI
> Swipe gestures to start and dismiss a task
> Fixing insets and task preview size
Bug: 75979063
Change-Id: Id402e6ac50551a7c0849742e3a0e77df3ead5aa2
> Removing hotseat from overview in transposed layout
> Removing face scrim from recents view in transposed layout
> Removing focued background from pagesView as individual poges have focus states
Change-Id: I620527241bf7240009c4187f53f5a5cff0c3e2b1
When you are in touch mode with Overview open, and press Tab or Alt+Tab,
it will be lost. This is because the upon pressing this key(s), app
gets switched to the keyboard mode. When this happens, the first
navigation ket gets ignored, and instead of navigation, we get focus
and highlight on the first focusable element.
The concept of the touch vs keyboard mode doesn’t fit well Overview
mode, hence the solution is to not let the recents activity to leave the
touch mode. We always keep RecentsView focused when visible. Android
honors the existing focus, and doesn't’ attempt transitioning from the
touch mode.
Bug: 73090995
Test: Manually fetch Overview, press Tab or Alt-Tab. Drag a task with
touch a bit, then press [Alt+] Tab. Repeat. Do the same with Overview
opened via Alt-Tab. Also: before, after and between, also check that Tab
keeps working on the workspace.
Change-Id: If6890ee80e08b03580051cceeac1be9a89ad3656
> Extracting common methods from Launcher & DragLauncher to base classes
> Remoting some dependencies on Launcher and using the base class instead
Change-Id: I121cacf8a14190b4703cda60bdeb4f79eee69ded
> Refactoring RecentsView to a common base class
> Moving some dependency form Launcher to BaseActivity
> Using the Recents view in RecentsActivity
Change-Id: Ie0e6741d356291e77420798c140c999121de3a0d
> Removing support for page drag-n-drop from pagedView
> Removing Overview UI from Launcher3 without quickstep and using options popup instead
> Removing touch handlers from CellLayouts and showing options popup based on workspace long press
> Excluding touch outside inset when showing the popup
Bug: 74136505
Change-Id: I34c2a7ff58452db26f5d1a85d554be40fc75f2b8
Swiping up for recents scales down workspace and hides it, similar to the transition
to all apps. Simultaneously, recents slides in from the side.
Also removed the setting for swiping to the first task, as it is required now.
Change-Id: Id0845db6650a37917a4faa9c8a434a2270913904
> Removing the widgets button from the card
> Making the height of the card same as that of the second card
> Using the same swipe rage for going between Normal and Overview state
Change-Id: Ib8bd050c52294bb01522fbcd0236f2221e6fe62d
We add a floating view for the menu that aligns with the task icon.
If available, the following shortcuts are present:
- Widgets
- App info
- Install (for instant apps)
It is designed to be straightforward to add to this list.
Bug: 70294936
Change-Id: I56c1098353d09fc564e0e92e59e4fcf692e486ba
> Tracking the touch from the start of the interaction, instead of when launcher is visible
> Animating the snapshot to the final posion after first draw
> Scheduling frame only when there are pending touch events
> Starting launcher before loading recents
Change-Id: Id9c3642ea235a1d35d31dbf28024c99dd4f47daa
When the touch passes a threashold, we take a snapshot and start the launcher
activity. The launcher displays the snapshot on top of its UI.
As we get further touch events, we move this snapshot and the hotseat in reponse.
Change-Id: I4623676227000afd52805a414a4de499081feced
In QuickStep, adding a placeholder ScrollView and changing the state logic
appropriately to handle that
Change-Id: I10223c0692788d6e5dbf8c408c01cafb4e39bd2c
