I really don't like the reactions stickied at the bottom of the screen.

nektro profile image Meghan Denny ・1 min read

I feel really bad this is my first post in a while, life's been really busy lately, but I just got the update that puts the article reactions stickied to the bottom of the screen (at least on desktop, haven't checked on mobile) but I really don't like it and it feels like a very unnecessary and unnatural too. After the article but before the comments is exactly when the user should be sending those reactions. After reading the whole article. And when you're reading the comments the reactions take up space because by then you already left your reaction.

I'll delete this tomorrow probably but I wanted to get my thoughts out there and see if maybe I'm thinking about it all wrong.

πŸ’– you DEV


markdown guide

I thought this too at first (hence the initial design), but got this request enough and started finding myself scrolling back up to reread something and then wanting to react where I was.

Anyway, I'm in favor of making this configurable in user settings. We currently don't have any UI settings really per se, but this could fit that use case.

This change could be entirely reverted with some CSS injection if you want to experiment with that yourself.


Interesting! I'll look into the user style and see if I go back, thanks for the quick response πŸ˜ƒ The CSS for anyone interested is:

.container .article-actions {
    position: initial;
    border: none;
    box-shadow: none;

There were also some other minor changes to the padding in order to get back to the original. But yeah, that's the basic adjustment. πŸ˜„

No guarantee this will never break but should be fine for the foreseeable future.


This post right now and,

  • The comments on this post,
  • Even the actual PR here discusses this.
  • All could have been turned into this changelog post instead to make sure everything was on one place.

It was a simple hack at start, now I am thinking of sticking it once it hits the end of the post. It feels fun to see things around. :D


How about stick it to the left ?

.container .article-actions {
  flex-direction: column;
  justify-content: space-around;
  width: 68px;
  height: 400px;
  top: 50%;
  left: 4px;
  transform: translateY(-50%);

I think your interpretation works as long as bookmarking isn't an action.

I can see two workflows here:

  • Click article
  • Read article
  • React to article (heart/unicorn)
  • Comment on article


  • Click article
  • React to article (bookmark)

As a habitual bookmarker, I'm one of the ones that needed bookmarking to be available anywhere. At its core, I don't care for reacting to be tied to bookmarking, but as long as those are considered the same thing, I love being able to react anywhere on the page as opposed to having to scroll past an article I want to read later just to flag it for later.


This depends on whether you use bookmarking as a way to remember good articles or save them for later reading. It would be interesting to see a convergence of these two where heart/unicorn/dislike stay in between the article and the comments with the bookmark moved off to the side but staying with the viewport as you scroll.


I made a Gitlab Snippet for that subset of "bookmark for later because it's a good resource" articles to keep my reading list purely "to read." It'd be nice if there was a way in site to do both separately, though.


After the article but before the comments

Personally agree with this sentiment. I think it would be cool to have it float until the comments, and then stay where it is. Overall though I'm a fan of the new change.


On mobile screen every pixel of the vertical space is important. Hate fixed and always visible bars


I didn't like it at first, but now I got used to it and actually like it. 😊