# \--header-offset with disposable top bar

**URL:** https://meta.discourse.org/t/header-offset-with-disposable-top-bar/286361
**Category:** Development
**Created:** [November 22, 2023, 7:18pm UTC](https://meta.discourse.org/t/header-offset-with-disposable-top-bar/286361 "2023-11-22T19:18:33Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![manuel](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/manuel/32/468169_2.png) [@manuel](https://meta.discourse.org/u/manuel)
#### Post date: [November 22, 2023, 7:18pm UTC](https://meta.discourse.org/t/header-offset-with-disposable-top-bar/286361/1 "2023-11-22T19:18:33Z")

</div>

I have a glitch related to header-offset with the [Announcement Bar](https://meta.discourse.org/t/announcement-bar/286352) component:

With the component enabled, `--header-offset` is calculated as 120px (header + top bar). On routes where the component is not shown the sidebar mostly adjusts, but sometimes stays with the offset. Not sure what’s the trigger, e.g. here’s different behaviour on different category lists:

Also, when I close the bar, the sidebar stays with the offset, until I scroll or change route.

Would I need to update header-offset manually? Or should this already be updated by default?
