Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 157 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

I've found that the vote counts in the question list on the Android app will gradually grow larger in size if I fling the list up and down, forcing it to scroll very quickly. I don't have a truly "scientific" method of describing this insofar as I cannot give you specific scrolling speeds or things of that nature. However, I can consistently reproduce the issue by simply flinging the question list up and down once or twice, with the issue becoming gradually more noticeable if I continue to fling the list back and forth.

To illustrate, here's what the list looks like normally:

enter image description here

...and here is what it looked like after I flung the list up and down several times in each direction. Notice that not only has all the text for the vote counts gotten larger, but it also appears to have grown to varying degrees (the '0' of the bottom question looks more clipped than the other two, for example):

enter image description here

Possibly also worth noting is that the answer count doesn't display the same behavior. This is version 0.1.53 of the app on a Nexus 4, running Android 4.3 (CyanogenMod).

share|improve this question
That's... That's... How does that even happen?! – michaelb958 Oct 25 '13 at 5:00
@michaelb958 This is totally a normal failure case for Android ListViews because they reuse list item layouts. So if you set the list item text size to textSize+=1 without checking whether its current size is already 24pt, it's easy to create this sort've problem. – blahdiblah Oct 25 '13 at 6:22
You... you... you flinged a hole in the space-time continuum? Õ_ô – Sumurai8 Oct 25 '13 at 6:23
Happening to me too. – Peter Cassetta Oct 25 '13 at 6:56
up vote 5 down vote accepted

Eek, that was an ugly bug. Thanks for the report, it's been fixed and will go out in the 0.1.54 updates coming out later tonight.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .