On Wed, 2005-03-02 at 09:44 -0500, Willie Wong wrote:
> Well known problem with firefox/gecko and /.
> IIRC it happens because the gecko engine starts rendering the content
> before receiving all of the data, which is not a particularly bad
> thing, because on most websites it means you will get to see the
> webpage a little earlier especially if your net connection is slow. 
> Unfortunately, with the way /. is written, while perfectly valid html,
> when the browser starts rendering too early, sometimes space are
> allocated wrong on the display agent (has something to do with the
> fact that the space for the side panels are allocated dynamically or
> something... anyway the important part is that the width for the side
> panels is not hard coded) and pushes content that comes in AFTER the
> rendering started to other places: i.e. to one of the black background
> areas around the border.
> Now if only slashcode is build using some sane CSS...

There might be a problem with "./" but this behavior wasn't effecting
Firefox 1.0.0 (at least in my case).
So Firefox 1.0.1 must have done some "negative" improvement that is
causing this effect :-/

gentoo-user@gentoo.org mailing list

Reply via email to