Change approach to layout in order to fix some weird CSS problems
authorSaman Bemel-Benrud <samanpwbb@gmail.com>
Wed, 24 Oct 2012 23:25:51 +0000 (19:25 -0400)
committerTom Hughes <tom@compton.nu>
Tue, 30 Oct 2012 13:55:14 +0000 (13:55 +0000)
commitb70aa5dbbde613e151a97da8dcf8855d2fffbebe
tree969a85a45f8f45174c381f9a49c622b38f98d5fe
parent0ba1839e78e694ab4ac1ca9fc650df1eec101b7c
Change approach to layout in order to fix some weird CSS problems

Move away from using an absolute positioned #content div as this was
causing some weird problems when users scrolled down, like not showing
bottom padding, and prematurely cutting off the left keyline.

Now, the content area uses relative positioning most of the time, and
fixed positioning when the full screen map is in place.

Using fixed positioning on the big map is nice because you can now scroll
down to see more sidebar content, but you won't end up with an ugly block
of white space under the map.
app/assets/stylesheets/common.css.scss
app/assets/stylesheets/large.css
app/assets/stylesheets/ltr.css.scss
app/assets/stylesheets/rtl.css.scss
app/assets/stylesheets/small-ltr.css
app/assets/stylesheets/small-rtl.css
app/assets/stylesheets/small.css.scss