android_frameworks_support/v4/java, branch cm-13.0 Unnamed repository; edit this file 'description' to name the repository. Reset SwipeRefreshLayout on window detaches. 2015-11-19T22:44:26+00:00 Aurimas Liutikas aurimas@google.com 2015-11-19T19:23:22+00:00 7c78904c44cfd4cef02e41ef3f341e9f87047d66 This fixes a bug when SwipeRefreshLayout gets detached when scale down animation is still playing causing onAnimationEnd to never get called. Bug: 21515801 Change-Id: Ieece09f8900fa47c14b81229490f047a55e156ba 
This fixes a bug when SwipeRefreshLayout gets detached when
scale down animation is still playing causing onAnimationEnd to
never get called.

Bug: 21515801
Change-Id: Ieece09f8900fa47c14b81229490f047a55e156ba
Merge "Make sure we honor canChildScrollUp()" into mnc-ub-dev 2015-11-16T09:07:53+00:00 Chris Banes chrisbanes@google.com 2015-11-16T09:07:53+00:00 b58b0d5a7ef0ef82db1840b4235fabe75d4832a4 






Merge "MediaBrowser: Handle null results properly in onLoadChildren" into mnc-ub-dev
2015-11-16T07:27:39+00:00

Sungsoo Lim
sungsoo@google.com

2015-11-16T07:27:39+00:00

11f682c4574b53ba6113bb811f197eadde491eb7












MediaBrowser: Handle null results properly in onLoadChildren
2015-11-16T06:01:28+00:00

Sungsoo Lim
sungsoo@google.com

2015-11-10T06:21:56+00:00

ae6d147640b8a868d2edff8ebac8d2a6bb03c594

- Allow to send results with null for notifying an error on loading
  media items.
- Add a workaround for the existing bug among API 21 - 23.

Bug: 19127753
Change-Id: I1507cf7b55fbc7187cf77801c3370ebb4cc3f614





- Allow to send results with null for notifying an error on loading
  media items.
- Add a workaround for the existing bug among API 21 - 23.

Bug: 19127753
Change-Id: I1507cf7b55fbc7187cf77801c3370ebb4cc3f614







Make sure we honor canChildScrollUp()
2015-11-13T15:01:22+00:00

Chris Banes
chrisbanes@google.com

2015-11-13T15:01:22+00:00

e1b81bbd6621232fa7ebcaf993bfe3aa7d472fbb

In the new nested scrolling flow we weren't
checking the callback. This CL adds it.

BUG: 25680804
Change-Id: I23cee7dde06b239195d02cd7ae7ab443b8769c36





In the new nested scrolling flow we weren't
checking the callback. This CL adds it.

BUG: 25680804
Change-Id: I23cee7dde06b239195d02cd7ae7ab443b8769c36







Merge "Add dynamic tab support to TabLayout" into mnc-ub-dev
2015-11-11T15:35:00+00:00

Chris Banes
chrisbanes@google.com

2015-11-11T15:35:00+00:00

d1639084dff2180f39f75deaf9faec34ae6541fe












Merge "MediaRouter: Black magic to bring custom media metadata back" into mnc-ub-dev
2015-11-10T04:09:18+00:00

Jae Seo
jaeseo@google.com

2015-11-10T04:09:18+00:00

6a184637de319a0db2b2d7299bca67ccd5d8f364












Merge "MediaBrowserCompat: Handle ServiceConnection methods in the given thread" into mnc-ub-dev
2015-11-10T03:57:26+00:00

Sungsoo Lim
sungsoo@google.com

2015-11-10T03:57:26+00:00

18341cb11f490d25a22dd2ff1c79a562531c0e6f












Merge "MediaBrowser: Publish the API" into mnc-ub-dev
2015-11-06T16:58:12+00:00

Jae Seo
jaeseo@google.com

2015-11-06T16:58:12+00:00

add8e891e1f91f348f29bd700382d2fc33b5579f












Add dynamic tab support to TabLayout
2015-11-06T10:59:20+00:00

Chris Banes
chrisbanes@google.com

2015-11-03T13:31:16+00:00

38cc44cffde90f6fe689b0df6b82f49481a981f7

TabLayout will now automatically invalidate
and re-populate itself when the linked PagerAdapter
has it's data set changed.

Two objects Pools are used to minimize churn when the
adapter is updated.

A small change had to be made to ViewPager + PagerAdapter's
observing functionality. Observable will always dispatch
changed events in reverse added order, which means that
ViewPager is the last to know. This means that any later
added Observer can't update the ViewPager (since it
doesn't know about the data set change yet). This is fixed
by moving ViewPager's observer out of the Observable and
always calling it first.

BUG: 20908355

Change-Id: I631620ff186047ae57e928db78f5ca77a0b80306





TabLayout will now automatically invalidate
and re-populate itself when the linked PagerAdapter
has it's data set changed.

Two objects Pools are used to minimize churn when the
adapter is updated.

A small change had to be made to ViewPager + PagerAdapter's
observing functionality. Observable will always dispatch
changed events in reverse added order, which means that
ViewPager is the last to know. This means that any later
added Observer can't update the ViewPager (since it
doesn't know about the data set change yet). This is fixed
by moving ViewPager's observer out of the Observable and
always calling it first.

BUG: 20908355

Change-Id: I631620ff186047ae57e928db78f5ca77a0b80306