GitLab

Bug: 20035978
Change-Id: I56a865262cd07e6af11b4374a7e6354710116dcd

- Issue: The fast scroller currently does not follow the touch input
  because fundamentally, the fixed scrollbar height and the mapping
  of the scroll space to the scrollbar space is fundamentally incompatible.
- This CL changes the fast scroller to allow it to detach when the user
  fast-scrolls, then re-attaches after the user scrolls the screen and
  the current scroll position for the scrollbar picks up the thumb position.
- Since the scroll position and the fast scroller thumb is now detached,
  we can change the distribution of the fast scroll letters to make it
  independent of the rows for each section and instead uniformly distribute
  it along the scrollbar, which allows for more stability.
- There are edge cases where this fails, especially when there are few
  apps, which we can investigate further.
  
Bug: 20035978

Change-Id: I8322f862107e6f330deff692885233706564bffd

Merge "Fixing empty screen created at the end, even when dragging the last item on the last screen." into ub-launcher3-burnaby

Merge "Deferring the move to the default screen until after we callback to the callbacks." into ub-launcher3-burnaby

- Since move to default screen starts the scroller immediately, any delays in
  handling onNewIntent and onHomeIntent in the callbacks will cause the scroller
  to skip frames the next time it updates.  This change will defer updating the
  page to the default screen until after onNewIntent is called back (and all its
  posted runnables).

Bug: 22929080
Change-Id: Ibab6106938721702d4da23faaca99039861e10dc

Change-Id: If0d4faf0ca15e71facb6ed2fd81ed6a589527836

  > Renaming Lmp to Lollipop
  > Lollipop_MR1 instead of directly using 22
  > Using M APIs directly instead of reflection

Change-Id: I10a307f46e3be15b3299f549a2fd7e0e215a6a1b

Bug: 23183034
Change-Id: I2b3f6f765a51edf75e666186650bbd3cf7b66a7a

Change-Id: Iedffa6e0a67907f0d86dfaf9b9863c4580cc3cf5
Auto-generated-cl: translation import

Merge "Disabling auto restore of widgets.   > Always show "Setup" button for a widget which has a config activity." into ub-launcher3-burnaby

  > Always show "Setup" button for a widget which has a config activity.

Bug: 23155863
Change-Id: I60683889e76be830a76ac1245e079574aaf0ad10

Merge "Reloading launcher whenever there is an external update to contentprovider, irrespective of the uri" into ub-launcher3-burnaby

Change-Id: If1a06da57171be30adb74f09ac256a8b03ab8549

Bug: 22293299
Change-Id: I64d5268cc263bbb6595a0b28bdd5ec73d540da41

Change-Id: I6b0d7c6db67ef4de9a6ee0b7752cccf070223df4
Auto-generated-cl: translation import

Bug: 20698931
Change-Id: I50bafac1fc0a855edb1ace633a8a6f87a5c3040e

This fixes perhaps an old bug.

If we started an accessible drag for an only item on a page,
then uninstalled the app while dragging, the page was removed
without unsetting its accessibility delegate. Later, the system asks
the delegate to do something, but the drag is over, and some pointers
are null, so everything crashes.

Fixing this.

Bug: 22028725
Change-Id: I85adcd42ae896603634994e20a7790792f7e84b1
(cherry picked from commit de1e67c3)

- Also show the search action when searching all apps

Change-Id: I3470b0da565e6d1bce637ce09384d966215a4ca7

Merge "Preventing zoom-in animation from running everytime the app updates." into ub-launcher3-burnaby

Bug: 22557455
Change-Id: I3ac1212a2f319397cd18be8f4452047d974312b8

Change-Id: I506948852945bfb8ebd7a95fc951880ffe9a3e17

Bug: 22293299
Change-Id: I6b9bf2b777d33ca23f291c7872ce1f338d41e516

- There was an issue with the previous logic where the test of whether
  the search bounds changed would always be false if valid search bounds
  were given.  This in conjunction with the fact that the padding was
  changed to only take the bounds left/right into account, meant that
  the container bounds would not be updated if the search bar bounds
  shifted via the insets.

Bug: 22918919
Change-Id: Ia810ddc7a56eae4afc0c7cd558fa6dc9e8e7a95b

Change-Id: I7f2e5a9aabdf1fc192ad7912aaefa3f41c059ff1

Change-Id: Id41615653cd4fa76213add4595418ad0cc6e7852

- We used to rely on the state transition to inflate the search
  widget after the permission to bind widgets was granted, which
  is fragile.  Now we try and inflate the search widget after
  user grants the permission if necessary.

Bug: 22515084
Bug: 22980143
Change-Id: Id111d263bc8a864e0fa652cfd0e07e66ec690fe7

Bug: 22980139
Change-Id: I87b633d194ff4e1529dd679dc02da573ed374207

Change-Id: Icb6b38f78aa56ad2c11e2ccc8005994ac4b86a91