SE is A/B testing a new solution where the voting buttons on an answer remain visible as you scroll down.

enter image description here

(I apologize for the running gif, it's super annoying, but it does the job).

Apparently the goal of this change is to increase voting, as the original post mentions that the acceptance criterion for the test is a 5% increase in votes.

The feedback so far is mixed, some people love it, others hate it.

From a UX standpoint, what could be the pros and cons of this?

  • 3
    I don't understand the point of it. What is the purpose? Why do I need it as a user?
    – Rob
    Jun 7, 2015 at 11:47
  • 1
    @Rob it's not 'for' the users. The point is that once you've finished reading the answer you are more inclined to vote because the vote buttons are visible, and not off the screen.
    – Andrew G
    Jun 8, 2015 at 2:05
  • 1
    @Andy Then that makes it for the users. My opinion is that it's a distraction, made me wonder why it was floating next to the comments as I scrolled down, and didn't make me want to vote.
    – Rob
    Jun 8, 2015 at 2:09
  • 2
    The current implementation is a bit annoying and distracting to some extent. The idea is good but the implementation is not not to the par.
    – Yellen
    Jun 8, 2015 at 10:35
  • 1
    How does it work when you scroll up the page? I read all the answers and comments and then scroll back up to the top to vote on the question or add a comment. Point being: I don't vote as I scroll down, usually as I scroll up. Jun 10, 2015 at 20:58

5 Answers 5


It's a good idea, but it needs some implementation tweaking I think

With a fixed voting console, it's easy to see how the console relates to the answer (it hangs off the top left so users know it relates to the answer)

Once the panel becomes sticky while scrolling, it visually detaches from that anchor so it's important to maintain visual-semantic relationship between the console and the answer.

Issues and suggestions:

  • Don't allow the panel to scroll into the comment part of the answer. There are several reasons for this:

    • Comments can be up voted so it creates ambiguity for the user to see a console on the left of a comment, and then also be able to vote on the comment separately. The nested up vote is confusing.
    • I think it's better to have users vote on the answer content rather than vote the comments. Comments often wander off scope, so you are more likely to get higher visceral votes or comment- rather than answer- driven votes if you allow the console to scroll down into the comments.
  • If you do decide to range-bind the console to the answer content, then make sure the top is properly grid aligned to the top of the content (it isn't today) and stops scrolling at the bottom of the content (excluding the share / edit / close console). This properly maintains the visual relationship between console and content.
  • I agree with tohster here. The vote control should stop above the comment area. To keep the content organized. Jun 10, 2015 at 1:39

Having control buttons in a fixed position is something quite common on today's web experience. You see the top navigation bar fixed at the top of a lot of news paper site and e-commerce sites. More annoying for some users (who don't use an AdBlock tool), is the fact that advertisement banners, usually on the right side of the page and not inline with content in some cases is fixed to the top while scrolling.

What is new here is that the buttons also fixes at the top of the page while scrolling downward in the same answer. These are inline controls and apart from sticky ads I think the experience from users will be positive, once you get used to it. It fix the problem scrolling back up to vote, and would probably improve the number of votes.

The con is that we are no longer looking at content in fixed position. This is especially true when asynchronous loading of pages mess up the current viewport and move what you're reading away. But the implementation here, doesn't do that cruel design choice. And we have been moving away from fixed pages since the introduction of scripted pages in the middle of the 1990s. This is another invention in that direction.

So from a UX perspective I believe it's a good thing where pros outrank cons.


I don't particularly like it. And the reason has to do with the visual separation of questions on a page. In short, the voting buttons are presently the most distinguishing feature identifying the top of a question and act as a very intuitive visual separator between questions. I found that when the voting buttons scrolled with the top of the window, I got confused trying to quickly navigate between questions because my first reaction felt like the questions themselves were moving around on the page.

The moving buttons add a whole new dimension of visual confusion that the brain has to process. It's an unnatural behavior the user has to be conscious of. That is, you simply have to be conscious and aware that the voting buttons are moving as you scroll or you will get confused very quickly while navigating.

Furthermore, by anchoring the voting buttons to the top of the window, the buttons for the current question will remain in roughly the same place on the screen the entire time (only to change briefly as a new question is scrolled in). This also makes it much less obvious when you've scrolled into a new question, unless you happen to be closely watching the voting buttons the whole time.

The human brain is very good at spatial visualization. By keeping with the "page" metaphor, where things are fixed on a single scrolling plane, the brain can visualize (to a degree) the entire document above and below the viewport as you scroll. But when the document changes as you move it, that impedes the natural spatial association of the document as a whole.

Just observe the animated GIF. It becomes very difficult to visualize the entire page as it scrolls, and to effortlessly discern the boundaries between questions.

I would argue that if the designers really want to do things this way, that more is needed than the current trial implementation. In particular, the voting buttons need to be conceptually separated from the post body (perhaps by having a darker background color in that column), and there needs to be some improvement made to the visual separation of questions.

For example, even something as simple as this could have a huge impact on the readability of the page with floating vote buttons:

enter image description here

Now even though the buttons are moving up and down within their column as the page is scrolled, the containing columns themselves are static, and since they are visually dominant, the brain has an easier time keeping the answers separated as the page is scrolled.

In short, the solution is to make the voting buttons less visually dominant. But being less dominant doesn't mean less obvious mind you. They're still obvious, but because they are contained in a visually dominating rectangle, the brain can tie that dominant rectangle to the page, and movement within that rectangle is not as distracting to the scrolling as a whole.


Personally I think it's a good idea although currently ther doesn't look to be much distinction between a question and an answer, which means the user could confused as to what they are seeing on the left hand side, maybe it needs better labelling or hierarchy applied?

Also in the case of a long answer versus a short answer, it doesn't hang around long on a shorter question, which makes sense technically but may confuse some users.

Like the idea though!


I feel like it would increase the likelihood of me clicking the wrong voting buttons because I'd have 2 sets of voting buttons very close together when reading near the end of a comment -- those for the current comment and those for the next comment.

Also, like others, I find the motion distracting.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.