I put my hands up, I should have read the specifications when writing this article. It was an oversight not to check and reference them (as they suggest this very concept). It would have affected the tone of five sentences in the third section.
But it wouldn’t have changed any of the substance in the article. The point stands:
“In general, this little bit of CSS trickery seems to have been discarded due to its incompatibility with IE5 and IE6”
Specifications are wonderful, but their implementation often isn’t.
@*Marc and Stefan*
That was my initial approach too. Two main reasons for ditching it; firstly you have a lot more trouble with manipulating the layout. For example adding a footer. Secondly, as soon as you start playing with the ‘overflow’ attribute in the main div the interpretation of ‘margin-left’ begins to differ in various browsers.
It reminds me of frames too. There were some instances when frames actually worked quite well; such as when viewing documentation with a large tree view in the left pane and the content in the right pane, that was one of the instances that I needed this layout for.
If you don’t want scrolling in your sidebar and you’d rather keep the browser scrollbar than the overflow scrollbar, you’ll probably need a different approach.
At least it’s fixed in IE7 :)
@*Dan, Fritz and Jack*
Yes, you’re right. Throwing 100%‘s into this causes further problems. It often does. Of course, you could probably just use the same techniques used in the layout to stretch the problamatic DIV to 100% without using percentages ;)