We're updating the mobile post controls layout to be more consistent with desktop

News and Events Announcements

AI-generated summary

The mobile post controls layout has been updated to be more consistent with the desktop version. awesomerobot shared a GitHub pull request and before/after screenshots, noting that the change aims to align the layout when the reply count is visible. For users who prefer the old layout, a custom CSS code can be added to revert the changes. b481 appreciated the option to revert and praised Discourse’s flexibility in allowing users to customize their experience. awesomerobot acknowledged the importance of balancing updates with user preferences and providing options for reverting changes when possible.

1

Today I’m merging an update that changes the default layout of the buttons under each post on mobile devices. This change makes our mobile button layout more consistent with desktop, especially when the reply count is visible (when the enable filtered replies view site setting is enabled).

https://github.com/discourse/discourse/pull/12760

Before:

Screen Shot 2021-04-20 at 5.50.41 PM
Screen Shot 2021-04-20 at 5.50.41 PM372×228 17.6 KB

After:

Screen Shot 2021-04-20 at 5.47.31 PM
Screen Shot 2021-04-20 at 5.47.31 PM373×227 17.2 KB

If you liked the old layout you can add some CSS to your theme to get back to it:

.mobile-view {
  .topic-post {
    nav.post-controls .actions {
      justify-content: flex-start;
    }
    &:not(.wiki) {
      button.reply {
        margin-left: auto;
      }
    }
    &.wiki {
      button.create {
        margin-left: auto;
      }
    }
  }
}

If you encounter any bugs that may be related to this change, please let us know!

34 Likes
2

Could that be one?

3 Likes
3

thanks for providing the CSS to revert, I get the desire to have a more consistent UI across platforms but I’m just way too used to the icons being on the left now :grinning_face_with_smiling_eyes: One of the best things about Discourse is that even though the devs are always updating, but it’s not forced and there’s almost always a pretty easy way to revert it if you prefer it.

5 Likes
4

Thanks for mentioning it! While we realize making changes can be disruptive to existing sites, we also don’t want to be stuck in a state where we can’t change things… so sharing ways to get back to the old behavior (when possible) seems like a reasonable middle-ground!

7 Likes