Recently there was a post that explains how views in Stack Exchange app are determined to be scrollable or not. Also, it fixed the issue on scrolling code-block horizontally on current design, which is lovely!

What surprised (and sometimes annoyed) me is, with very-specific method, now I can scroll all some1 posts (yes, post, not only code-block) vertically, inside its individual container regardless of the length of the post. And it randomly occurs, even on the same post.

Steps to reproduce:

  1. On the post body, slide horizontally a little bit (you can also do it on code-block to make it easier to see)
  2. While still holding your finger on the screen, slide vertically.

What happens: The post is scrolled vertically inside the container, perhaps due to the fact that the actual height of the content is actually much taller than the container.

Side effects: Sometimes, the touch event won't be registered (e.g. cannot pop-up the code-block when it's tapped, cannot open the link on the post). Example link.

This is a code-block. You should be able to tap on it to open in pop-up. If you cannot open it, then it is the side effect of this bug.

What I expect: Well... I don't want to scroll the post inside the container, I want to scroll the whole thread instead.

Proposal: Disable vertical scrolling on individual post at all, since code-block is always expanded regardless of the length (i.e. no scroll-bar for tall code-block, compared to on browser).


  • Stack Exchange: 1.0.57
  • Android model: Nexus 4
  • Android version: 5.0.1

1. As of current, I haven't found the criteria for this bug to occur. At least a post that can be displayed wholly on the screen is facing this issue. On the other hand, if the side effects occur, then the post is also facing this issue.

marked as duplicate by Kasra Rahjerdi Mar 17 '15 at 22:19

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

  • You can try it on this post. I'm afraid this might be device/Android-dependent, so any feedback are useful. – Meta Andrew T. Feb 18 '15 at 6:18
  • Hmm, I'm not able to repro this on my Nexus 5 running 5.0.1 -- Has anyone else been able to repro this? – Kasra Rahjerdi Feb 18 '15 at 18:31
  • As I now have Nexus 5 on Lollipop 5.1, the issue didn't occur on this device. Might be an issue on Nexus 4 on Lollipop... not sure yet though. – Meta Andrew T. Mar 17 '15 at 19:54
  • 1
    I just repro'd this (on this question) on a Galaxy S3 running 4.4.2, yay! – Kasra Rahjerdi Mar 17 '15 at 21:37
  • 1
    Marking this as a dupe of a similar bug, expect an answer to both soon! – Kasra Rahjerdi Mar 17 '15 at 22:19

Browse other questions tagged .