# Why doesn't Discourse use position:sticky for the top header?

**URL:** <https://meta.discourse.org/t/why-doesnt-discourse-use-position-sticky-for-the-top-header/101960>\
**Category:** UX\
**Created:** [13 בנובמבר,‏ 2018,‏ 6:24pm UTC](https://meta.discourse.org/t/why-doesnt-discourse-use-position-sticky-for-the-top-header/101960 "2018-11-13T18:24:27Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [13 בנובמבר,‏ 2018,‏ 8:37pm UTC](https://meta.discourse.org/t/why-doesnt-discourse-use-position-sticky-for-the-top-header/101960/4 "2018-11-13T20:37:25Z")

</div>

That bug is completely unrelated to sticky, it happens cause of this

> **[requestAnimationFrame based rendering](https://discuss.emberjs.com/t/requestanimationframe-based-rendering/14284)**
>
> Recently I learned about: https://bugs.chromium.org/p/chromium/issues/detail?id=570845#c9 Chrome 47 has a new feature which lowers the priority of timers during active input when the timers appear to be SO expensive that we can’t run them while...

It will eventually go away, oddly enough, when we rewrite our timeline in ember, cause now we pay a big tax on

It is possible, I guess we can work around the chrome timer bug by adding sticky to chrome for the timeline 🙂

---

_[View the full topic](https://meta.discourse.org/t/why-doesnt-discourse-use-position-sticky-for-the-top-header/101960)._
