You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While respecting paddingTop/Bottom is good, RecyclerView does draw in the padding if clipToPadding="false" is specified (and this is important for use cases like reserving some bottom space for a FAB, so that the last list item can always scroll above it and be fully visible). In this case the library should also draw in the padding. That is, the fix in 472ee5f should be applied only when View.getClipToPadding() is true.
The text was updated successfully, but these errors were encountered:
Does this also fix the touch issues? Currently, with clipToPadding="false", the scroller is drawn correctly (with the same padding), but it still treats touch input as though there is no padding (and thus you have to drag your finger further than where the scroller is drawn).
While respecting paddingTop/Bottom is good,
RecyclerView
does draw in the padding ifclipToPadding="false"
is specified (and this is important for use cases like reserving some bottom space for a FAB, so that the last list item can always scroll above it and be fully visible). In this case the library should also draw in the padding. That is, the fix in 472ee5f should be applied only whenView.getClipToPadding()
istrue
.The text was updated successfully, but these errors were encountered: