IssueTracker

If you need that View to always be visible then it shouldn't be contained within the scrolling view (the one with the scrolling Behavior).

I have the following situation:
Activity with this structure
CoordinatorLayout
  AppBarLayout
    Toolbar
    TabLayout
  ViewPager - uses AppBarLayout.ScrollingViewBehavior

inside the ViewPager I'm displaying my fragments

one fragment contains simply a RecyclerView
the other fragment has a RecyclerView and a bottom view that should always be visible

since the ticket is marked 'WorkingAsIntended' - how do you suggest we get the desired behavior?

since you wrote that the bottom view should be contained inside the scrolling view I moved the view to the activity - and i make it visible and the anchor of the pager in it's original fragment and gone in the other fragment.

This doesn't work well -
the transition between the tabs doesn't animate properly and also it disappears after  changing orientation - and there are other issues with it that might be related to issue - https://code.google.com/p/android/issues/detail?id=175243

also this feels wrong from the design aspect - why would it be in the activity if it is relevant only to one fragment

I uploaded the xmls that I'm using here - can you take a look and let me know if it is possible to get the behavior that I'm looking for with a CoordinatorLayout?
https://drive.google.com/folderview?id=0B1MnnD7rqBMWfnhVTmtJWThmMDBLSEUwT255d2RKZHZic2JjWkFZNkJ4VFJaa1RhYmdSQ3c&usp=sharing

 chrisba...@google.com ,


<FrameLayout   (scrolling behavior)>
 <RelativeLayout (scrolling behavior)>
     <RecyclerView (scrolling behavior)/>
     <LinearLayout/>
 </RelativeLayout>
</FrameLayout>

In this case LinearLayout should be always visible right? Well it's not.

This is bug. If it's not, then How about a sample how it should be done???

No it's not a bug, it's working as intended.

The fix is simple, don't put your footer within the View which is set with the scrolling behavior.

Ohh really? Using Fragments is impossible then. Or you offer me to add some dynamic padding to FrameLayout or ViewPager since android:layout_below="@+id/appBarLayout" dose not work?

Using in Fragments is giving issue as can be seen in the following repo:
https://github.com/varunrramani/HideOnScrollIssue commit id: 2c2da171dee589c5cdc6589f5ec5ae375dc01e48

If this is not a bug, then ViewPager is useless in this scenario. As I can see, and I came across the same bug, the ViewPager should not use the Scrolling behaviour, but if it doesn't have it, then the CoordinatorLayout simply overlaps it with the tabs or toolbars you put on top.
I tried a setup similar to Kirvis, obtaining the same results :
<CoordinatorLayout>
    <Toolbar/Tabs>
    <ViewPager (scrolling behavior)>
        <RelativeLayout> <----- One of the tabs
            <RecyclerView (scrolling behavior)>
            <LinearLayout>

I've the same problem...

I've the exact same problem!
And yeah this solution is useless in for Fragments, I can't move that Layout from Fragment to ParentActivity, it's not its responsibility.
Please do post if anyone has solution to this apart from hacky one like adding padding/margin to bottom component.

this is the solution that i found to the issue i originally posted (it does contain changing the padding)- http://stackoverflow.com/a/31140112/2482564

Based on #12's solution, I came up with the following. It works well when scrolling up and down with the finger, but it doesn't work as well when releasing the finger and allowing the app bar to animate open or closed, even though the numbers seem to line up based on logs. In this case, the padding doesn't align the bottom of the viewpager's content exactly with the bottom of the screen. I'm not sure why that is and would be happy for any feedback.

public class CustomScrollingViewBehavior extends AppBarLayout.ScrollingViewBehavior {
    public CustomScrollingViewBehavior() {
    }

    public CustomScrollingViewBehavior(Context context, AttributeSet attrs) {
        super(context, attrs);
    }

    @Override
    public boolean onDependentViewChanged(CoordinatorLayout parent, View child, View dependency) {
        boolean result = super.onDependentViewChanged(parent, child, dependency);

        final int totalScrollRange = ((AppBarLayout) dependency).getTotalScrollRange();
        final int bottomPadding = totalScrollRange + dependency.getTop();
        child.setPadding(child.getPaddingLeft(),
                child.getPaddingTop(),
                child.getPaddingRight(),
                bottomPadding);

        return result;
    }
}

I found a workaround for #13, not one that I'm entirely happy with but it's doing the trick for me. If there's a better way to do this and still accomplish the goal that the OP and myself are after, I'm all ears.

http://stackoverflow.com/a/33396965/1317564

Please visit this question to help me with the same problem:

http://stackoverflow.com/questions/35576290/fix-bottom-bar-in-coordinatorlayout

I have created a fix, which basically removes scrolling flags and overrides offsetting scrolling view when scrolling content is within bounds of scrolling view. It works for your footer and also for view pager. https://gist.github.com/MaciejKaras/02bff315f00b87d80467a470424f22c3

I have same issue, only with FAB. My hierarchy is:
<CoordinatorLayout
  <AppBarLayout
    <Toolbar app:layout_scrollFlags="snap|scroll|enterAlways"
    <TabLayout
  <FrameLayout app:layout_behavior="@string/appbar_scrolling_view_behavior"

and Frame layout is container for viewpager, which contains fragments, one of which contains recycleview + fab. see attachments.