Thanks for the tips. I opted for that .content_scroller because when the whole body was scrollable the side menu was really jumpy and glitchy on the Android phones I tested on. It also was doing weird things with the address bar, hiding and showing it in a seemingly random way.

I think you mean `position: fixed` rather than `display: fix` right? In which case the side bar class .side_bar_column already has that. Unless you mean a different class/element?

Anyway looks like I'll have to attack this scroll issue a little more systematically. People usually complain about scrolljacking. I'm doing the absolute opposite, trying to let browsers do their thing themselves, but apparently that's bad too lol. Can't win.