# Absolute/relative position of FF UI urlbar

**URL:** <https://discourse.mozilla.org/t/absolute-relative-position-of-ff-ui-urlbar/141302>\
**Category:** Development\
**Created:** [March 12, 2025, 6:18pm UTC](https://discourse.mozilla.org/t/absolute-relative-position-of-ff-ui-urlbar/141302 "2025-03-12T18:18:21Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kein](https://avatars.discourse-cdn.com/v4/letter/k/e79b87/32.png) [@Kein](https://discourse.mozilla.org/u/Kein)\
**Post date:** [March 12, 2025, 6:18pm UTC](https://discourse.mozilla.org/t/absolute-relative-position-of-ff-ui-urlbar/141302/1 "2025-03-12T18:18:21Z")

</div>

I’m a bit puzzled by some weird behavior I’ve encountered on Firefox 136 when using custom UI css rules (via `userChrome.css`).  
This (making urlbar toggleable and in “overlay” mode) used to work just fine in FF 132:

```
toolbar#nav-bar
{
	top: -99px; 
    position: absolute;
	height: 0px!important;
	min-height: 0px!important;
}

toolbar#nav-bar:focus-within,
toolbar#nav-bar:hover,
toolbar#nav-bar:focus
{
	top: unset;
    position: absolute!important;
	height: unset!important;
	min-height: unset!important;
}

```

However, after updating to 136, I’ve noticed weird behavior I can’t comprehend - after focusing (via CTL+L) the urlbar to bring it on top and **then clicking any of the extension icons** - default CTRL+TAB to switch tabs simply stops working. At all. Period. The moment I remove `position` rule (i.e. it always stays relative) - everything works just fine.

&nbsp;

I’m out of ideas myself so I’m curious if anyone else can figure this one out.

&nbsp;