BUG REPORT: scrolling makes the position: absolute; dropdown box move around the pageRESOLVED FIXED: changed position: absolute; to position: fixed;BUG REPORT: scrolling down before opening the dropdown box makes it appear further down the page based on how far the user has scrolled down.

Also, you are wrong. I fucking hate fixed-top titlebars. Because 99.999999% of them take up at least 25% of the screen, which cuts down on my already limited vertical real-estate. I don't need shit floating overtop of what I'm reading. Especially when I scroll down, and the line I last read goes behind the titlebar. Normally I'd just scan the top line at the top of the browser window to see where I am. Not anymore. Now I need to look at the top of the browser window, realize that isn't the top of the page, then look down to find where the top line is. It breaks muscle memory. Therefore it is bad.

Also it breaks in-page searching, since if the word you're looking for is behind the floating header, you will never see it highlight.

And if I want something in the header, I'll press HOME or CTRL-PGUP. I have never once needed something in the header when I was mid-page.

@ben_lubar This further cements my resolve that anyone using position:fixed for anything is doing it wrong and needs to stop doing whatever they are doing.

fixed is the correct position here, I think, they just need to set the menu's top correctly.

I believe that absolute would be preferable. The problem is that the autocomplete elements are essentially siblings of the composer control when they should be descendants of it. With the element hierarchy that is in place, there isn't really a "great" solution.

@abarkerabsolute only works when it's the child of descendent of relative, otherwise it'll be absolute relative to the body element. Either way, it's subject to moving when you scroll, which fixed isn't, as that is relative to the window, not the document.

Besides, the issue isn't fixed vs absolute: the issue is the auto-complete always appears below, even when there isn't room.

Either way, it's subject to moving when you scroll, which fixed isn't, as that is relative to the window, not the document.

That depends on what it is positioned relative to. If the auto-complete dropdown were absolute and a descendant of the composer area, it would not change position when the thread is scrolled. Depending on exactly how the structuring was done, it might change position based on the scrolling of the editor, but that might be considered desireable UI because it would keep the dropdown next to the point of insertion.

But because the auto-complete elements are not descendents of the composer, all that goes out the window. You can't easily keep the dropdown near the point of insertion (especially since every dropdown has a unique ID). Any changes in window size completely screw you over. And so on.

After a quick experiment with Chrome's dev tools, it looks like the dropdown can be moved into the composer element and set to absolute without breaking anything. That will fix the scrolling-with-body issue properly, and make solving the appear-out-of-frame issue easier to solve (I think).