# Near Real-time Discussions (not chat) - Optimizing Features

**URL:** <https://meta.discourse.org/t/near-real-time-discussions-not-chat-optimizing-features/32349>\
**Category:** Feature\
**Tags:** planned\
**Created:** [21.Август.2015 00:44:16 UTC](https://meta.discourse.org/t/near-real-time-discussions-not-chat-optimizing-features/32349 "2015-08-21T00:44:16Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![fefrei](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/fefrei/32/119538_2.png) [@fefrei](https://meta.discourse.org/u/fefrei)\
**Post date:** [21.Август.2015 20:04:18 UTC](https://meta.discourse.org/t/near-real-time-discussions-not-chat-optimizing-features/32349/15 "2015-08-21T20:04:18Z")

</div>

Maybe we could try to increase the chances of the user having scrolled down far enough with a bit of simple trickery?

Currently, when the composer pops up, it covers the lower parts of the screen – making it more likely to cover the end of the last post. If we added an auto-scroll that (smoothly) scrolled down half the composers height, this would mean that the composer gets half its screen estate from the top, half from the bottom. To me, this makes sense from a UI perspective (it’s “fair”), and increases the chances of the first new post being visible.

It’s also familiar: At least iOS likes to do this auto-scrolling when the keyboard pops up.

---

_[View the full topic](https://meta.discourse.org/t/near-real-time-discussions-not-chat-optimizing-features/32349)._