The fix is too big to post, as the layout needs to be changed so the sidebar reflects responsive positioning, which means changing most of the basic CSS. I don't believe Chris needs a fix from me for that, as he is quite competent in writing CSS. The mistake is the order, thus the CSS reflects that currently. The wrapper css would need a rewrite to be functionally responsive compatible, then every main template using it would need tweaks and their CSS primarily.
Even the resource manager... the sidebar is left positioned, and it comes first in the code, it isn't hacked into it after the code by trying to reposition it before the main container, that is why it works on the left side with the main container right. Responsive design must work to a natural order, otherwise you get issues with right margins.
Moving a left column to the bottom on mobile view is easy, just like the resource manager does, after the fact. Moving the left column into the left position, as the media add-on does, is a nightmare for all the reasons mentioned above already. Responsive design has a precise method for all these reasons. When you screw with the natural order of collapse, you have to hack, hack, hack, and even then, you will be hacking ongoing to constantly fix small border widths, padding or margins throwing out to the right on mobile viewing.
Oh... don't get me wrong, I also understand that this was written for 1.1.x, not 1.2 responsive... and that is the real reason the issue exists. My point is that this is responsive now, and as such, its needs to be done correctly. My users expect fairly high standards, professional features and feel, and if I can't give them things with mobile viewing issues, when most users are today viewing this stuff through their tablet or mobile, they don't like it.