Chris Hoess <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> 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
> 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 prepared new file with interactive js-confirms, so no need to comment
out anymore.
http://my.tele2.ee/cadorsoft/unresolved/testbug_wide-image-in-clipped-div-ve
rsus-scrollbars_ChrisHoess.htm
I have additional questions written there in bold.
I definately don't want to use fixed positioning by creaton of child
element,
since this puts by my Moz0.9 the inner red div to the left top corner of
browser and
secondly comes the fact, that the inner DIV W O N T M O V E also
when I move the outer DIV.
The inner DIV still stays at its position in browsers upper left
corner...
And thirdly fixed positioning doesnt work anyway by msie5 too...
My goal was to shift the inner DIV to the left or right with script to
imitate text scrolling or
something like that. The outer DIV, which should have had the
possibility to move
anywhere in the document was meant to sarve as a "small screen" where
the
part of text from inner DIV will be made visible... So the absolute
positioning is IMHO
in its right position and correct, when I want to achieve the
functionality above described...
> 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 am not a native English speaker, I dont get quite now what You are
stating...
The second DIV i s n t created with fixed positioning in the corner of
the div....
I thought with my head, I dunno the fancy standars, but my arguments
were:
1.) when I click outside divs clipped region, the events wont fire
for div, even
if the mouse finds itself in the rectangle where the DIV would
stay, when it wouldnt
be clipped...
2.) You cant/shouldnt see any parts of child elements whatsoever,
that are
"descendants" of clipped DIV and are outside parent DIVs
clipped region.
3.) Based upon that, the scrollbar, that appears at "body - top
level", cannot
help in any reasonable way to show/scroll the contents, that
is in child element of clipped DIV.
So that makes the scrollbar useless and logically thinking, IHMO
it should
be hidden/ stay hidden in the first place, cause it is quite
USELESS...
=====
so why to show the damn scrollbar ? If this is because of CSS2 spec,
then I guess
this specs logic is a bit odd for me... ;-]
--
position: absolute / obsolete, whats the difference anyway...
MM anno MM(I) aus Estland;
http://my.tele2.ee/cadorsoft/links2PROJECT6.htm
