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

Attempting to use the site with a Nexus 4. I came across a question that was a duplicate, so I found the dupe and voted to close.

The only problem: the button is at the bottom of the modal. While in mobile view, that means lots of painful scrolling all the way through the question and its answers.

On the normal site this isn't an issue:

This is normal and okay - you don't have to scroll through the question.

...but on the mobile site...

It's all the way in the bottom corner!

Here's an example:

This definitely affects usability while on mobile.

share|improve this question
Yes! I am on mobile a lot, and this bugs me, but I keep forgetting to report it! Also; I wish I could do such pretty freehand... – Andrew Barber Mar 13 '13 at 9:38
I added an example about the scrolling nightmare. This needs to be fixed—it's excruciating. – slhck Mar 29 '13 at 12:03
My proposed solution to this is just don't show the answers at all. – animuson Aug 9 '13 at 18:42
@Sklivvz Oh come on, how is this not a (usability) bug? Compare it to the desktop version — the window for the duplicate question is height-limited and it doesn't require you to scroll all the way to the bottom just to find the link. – slhck Jul 5 '14 at 14:34
Strongly agree that this is a bug not a feature request. The mobile skin is missing a suitable implementation of this existing feature, so loads one that is not fit for purpose. – IMSoP Aug 2 '14 at 9:02
@IMSoP bug is when the intended behavior is not working as expected. In this case, the position of the button and the scrolling is the intended behavior. No bug here. – Shadow Wizard Aug 5 '14 at 10:49
@ShadowWizard I'd be surprised if the position of the button is intended behaviour rather than a side-effect of implementation. In the desktop UI, the close button is visible at all times, with no scrolling required. The mobile UI appears to be identical, but without the additional scrollbar; the button is in the same place, but now you have to scroll miles to reach it. – IMSoP Aug 5 '14 at 12:39
@IMSoP the developer who is writing the code changed from bug to feature request so it's all the proof we need. Not saying I support this and I also want it fixed, just explaining. – Shadow Wizard Aug 5 '14 at 13:09

You must log in to answer this question.

Browse other questions tagged .