In article <3b5893fb$0$32924$[EMAIL PROTECTED]>,
Roland M�sl wrote:
> "Ian Hickson" <[EMAIL PROTECTED]> wrote in message
> [EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
><> Show me the standard where is written
><>
><> "When overflow:auto, show a blank screen"
>
><As David Baron has explained on the bug, this only happens because the
><element is empty of in-flow children, since all the children are
><absolutely positioned. I'm not exactly sure what you were trying to do
><with the 'overflow:auto' but whatever it was, the way you are doing it is
><wrong. Mozilla is laying this out correctly as far as I can tell.
>
> You try only to discuss away the bug
> by numerouse word plays.
Let me point out, before we go further, that both Mr. Hickson and Mr.
Baron are Invited Experts on the W3C CSS Working Group: that is, they are
part of the team *designing the CSS3 standard* because *they have
demonstrated an excellent command of CSS1 and CSS2*. This rather weakens
your claim to understand the spec better than they do.
So far as I can tell, the state of standards with regard to laying out
your page is roughly thus:
IE: not compliant. As explained above and in the bug, IE doesn't realize
that <html> and not <body> is the root node of the page, and doesn't apply
overflow:auto to it correctly. Admittedly, this is somewhat
understandable, as ignoring <head> for rendering purposes would have been
a reasonable shortcut before CSS2, but it's rather disturbing to see that
this bug has persisted.
Mozilla: better, but still buggy. Mozilla tries to correctly implement
the CSS spec: because the only contents of the <body> element are
absolutely positioned, they *do not count* in deciding how large to make
<body> (see various quotations from the spec), so <body> should have
a height of 0. However, for some reason, some information from the
non-overflowed layout is leaking through, so that the links and cursors
are still changing. This is indeed a bug; that should not appear.
> But You had been unable to read my original post
> I wrote there
>======================================
> When You move the mouse around over the black
> area, the mouse pointer changes when You are over
> a link.
>======================================
>
> This means the whole page is rendered.
> All the links are at the correct position.
>
> This can be easy prooven by moving the mouse
> around. Where ever a link is, the mouse changes
> to the hand with the finger like over an link.
>
> The only problem is:
>
> The colors do not match the CSS.
> Everything is written in the background color
When I set the background color to "transparent", nothing appears. Given
the nature of Mozilla's rendering architecture, I think it is far more
likely that there is an error in the clipping of the <body> element than
that every child element has had both "color" and "background" set to
black.
> I am curriouse how You will atempt to
> dicsuss away this failure.
>
See above. I will comment in the bug to update the true nature of the
problem.
--
Chris Hoess
