# Improving our "lowest read position" Back button / indicator

**URL:** <https://meta.discourse.org/t/improving-our-lowest-read-position-back-button-indicator/54324>\
**Category:** Feature\
**Created:** [16 Diciembre, 2016 01:28 UTC](https://meta.discourse.org/t/improving-our-lowest-read-position-back-button-indicator/54324 "2016-12-16T01:28:23Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\
**Post date:** [20 Diciembre, 2016 01:04 UTC](https://meta.discourse.org/t/improving-our-lowest-read-position-back-button-indicator/54324/4 "2016-12-20T01:04:05Z")

</div>

OK! We went through a round of feedback on this as well. Give it a try and see what you think. Should be a lot easier to find your way **back** to your lowest reading position, particularly on longer topics where it is needed the most.

Also, this article was really interesting on the philosophy of what the back button means and what users expect it to do:

> **[4 Design Patterns That Violate “Back” Button UX Expectations – 59% of Sites...](https://baymard.com/blog/back-button-expectations)**
>
> Our large-scale usability testing reveals that users expect the "Back" button to take them back to what they perceive to be their previous page, which often differs from site behavior.

---

_[View the full topic](https://meta.discourse.org/t/improving-our-lowest-read-position-back-button-indicator/54324)._