@Tsaukpaetra The formatting buttons used to not work at all if you selected a trailing space. @ben_lubar tried to fix that here. He moved the formatting characters (*, ~, etc) before the trailing space, but that doesn't change the length of the selected text. The ins/del button uses the length of the selection to position the cursor, and it can't do it correctly because it doesn't know that the trailing space was moved.
@pydsigner probably at some point the highlight quoter was modified to restrict its selection to the post's main content element. The raw element is outside of that, so it's seeing nothing and quoting the whole post.
@boomzilla yes, the view raw script was something I'd written in my userscript. I'd originally made it a button next to "reply", but people complained that it broke their "click first blue button to reply" workflow so it was moved under the menu instead. Also the reply as topic option was from my userscript, and shared some of the same code (it also has to fetch the raw post to quote it).
It's a semi-enclosed room, typically a porch that has been enclosed with walls and screens and had ceiling fans installed. They give you the feeling of being outdoors while keeping the bugs away and typically being a bit cooler than out in the direct sunlight. Some Arizona rooms can be completely closed up during cooler weather, turning the room into a cross between a greenhouse and a patio.
My sister's place has one of those, except they're in Utah so it was designed with the opposite goal in mind: keep out the snow!
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).