In article <9kso78$6d0me$[EMAIL PROTECTED]>, Marek M�nd wrote: > Please post any comments regarding to that browsers > de facto logical design bug concerning about > layers, clipping, scrollbars and overflow: > > http://my.tele2.ee/cadorsoft/unresolved/testbug_wide-image-in-clipped-div-ve > rsus-scrollbars.htm > > (2,11 kB HTML data ) > If you find it also horrible and against any reasonable logic, > please file it at bugzilla, so that this will be fixed. This is not a bug. By commenting out the clip (which does *not* affect scrollbars, which is correct by CSS2) and replacing the img by a div with background, you can get a much clearer idea of what's going on. I think the point at which what happens diverges from what you expect to happen is in the creation of the child element, on which you've set "position: absolute" and "width: 0px", among other CSS properties. Position: absolute causes the new element to be created *relative to the containing box* (your green div), so that 0px *puts it in the corner of the div, not the viewport*. What you probably want to do is use "position: fixed", which does place the element relative to the viewport, so "top: 0px; width: 0px; position: fixed" would create an element in the upper-left hand corner. In this case, the 2nd element is being created in the corner of the div; the div is shoved 600 px over, then the 2nd element (which has width 350, from the original setting of the div) is shoved over another 600 px, and a scrollbar appears. I hope this helps. > p.s. In case there are Netscape6/Mozilla geniuses, please explain me > why those two <button> elements look so horrible ? See the other reply to this in the newsgroup. Have a nice day! -- Chris Hoess
