Since Google has published the design support library for android, there are many nice things that can be done without implementing custom code. While i’ve tested the custom views in this lib, i have found a worse thing, and i didn’t know if this is a bug or not.
I have found the cheesesquare project on github. In the activity_detail.xml(layout file) there are 3 CardViews inside the NestedScrollView. If you delete 2 of them, you can see that the NestedScrollView doesn’t have the full size of the parent(match_parent). The NestedScrollView is bound to the bottom of the parent view. http://i.stack.imgur.com/BXl7w.png
The NestedScrollView get’s his full size when i remove the
But when i remove the layout behavior, the toolbar is not collapsing.
Is there any fix for this? Example layout file can be found here: https://github.com/Smove/cheesesquare/blob/stackoverflow/app/src/main/res/layout/activity_detail.xml
You can build the cheesesquare apk from my github branch
I had this problem and fixed adding:
to the NestedScrollView. Then it starts behaving correctly, as I explained here also. Of course the NestedScrollView needs some kind of child (i.e. it must not be empty), otherwise the toolbar won’t collapse.
While this works well with small content, I noticed it has some problems showing longer contents, e.g. like the full
activity_detail.xml above. The problem is that you can’t scroll to the very bottom part of the content – it is unreachable at the bottom.
From my tests I could find that the missing part is as big as the collapsed toolbar (or at least that’s what it looks to me). To fix this is issue, and having a solution reliable for both small and big contents, you should add a
layout_marginBottom to the ScrollView, so that it gets measured and releases the missing bottom part. Thus:
or whatever size you gave to the
Scrolling with small contents with this solution, even if the content is justly aligned at the top, isn’t really smooth as scrolling with large contents. I’ll use until a library fix comes.
Looks like this was fixed in v22.2.1 .
Before showing my NestedScrollView and after binding the data to the NestedScrollView content, I call the method fullScroll(int direction) of my NestedScrollView instance with the View.FOCUS_UP direction as argument.
Code example for a fragment:
NestedScrollView scrollView = (NestedScrollView) getActivity().findViewById(R.id.scroll_view);
use RecyclerView replace NestedScrollView fix this bug
set item count 1,that ViewHolder return your real contentView;