I've removed the overflow for now.

I see your point but I don't share your conclusion. If you have right 
aligned code like you describe, with the original layout, you don't 
see it on the screen, but you see the scrollbar and know that there is 
more to look for. But now, if you have long source code like in the 
example link, you still don't see it completely on the screen, but you 
don't see the scrollbar either, having no visual hint that there is 
more to see somewhere.

I don't understand the applicability of that URL to the source viewer.

What about similar solution, but only with horizontal scrollbar and 
without sidebar divs? -> http://www.tv1.lt/new.html

I agree it''s not ideal - ideally we could say height:100% or 
something and it'd go to the bottom of the window and then put the 
scrollbar there - but CSS unfortunately won't let us do that unless we 
set a fixed height.



I understand the concern, but this prevents layouts from going really 
wacky in some cases. Take the example of a piece of code attached 
inline to an email - without the overflow, anything on the message 
view screen that is right-aligned is going to completely disappear. I 
found that much worse than having the horizontal scrollbar just at the 
bottom of the code.

That's on purpose and it never was different in the past. What has 
changed though is, that you no longer scroll the complete page but 
only the source code block. This is nice, because you always have the 
line numbers in the view, but OTOH it's quite irritating, because you 
only see the horizontal scrollbar if you scroll to the very bottom of 
the page. If you don't recognize the scrollbar, the source looks cut 
off.

Chuck, I think we should revert this behaviour.

File source in checkout screen is not wraped in IE. For example: 
http://cvs.horde.org/co.php?r=2.772&f=imp%2Fmailbox.php