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... W On Wed, Mar 02, 2005 at 07:17:39AM -0700, Joseph wrote: > After upgrade to Firefox 1.0.1 when I try to reload slashdot page "./" I > usually need to hit "reload" button twice. The first time it display > empty page (just the frame) after second click it display the page > correctly. > > Did anybody experience this strange behavior? > > -- > #Joseph > -- > [email protected] mailing list -- ---------------------------------------------------------------- * Address: 45 Spelman Hall, Princeton University 08544 * * Phone: x68958 AIM: AngularJerk * * E-mail: [EMAIL PROTECTED] From: sep.dynalias.net * ---------------------------------------------------------------- If a man watches three football games in a row, he should be delared legally dead. ~Irma Bombeck Sortir en Pantoufles: up 7 days, 6:05 -- [email protected] mailing list
