/. are the geek mecca. You cant seriously expect them to bother with such trivialities as "standards" :P
Incidentally, you can disable the behavious you mention, although the strange thing is that by default it is disabled. IE firefox waits for a period of time before starting to render the page. This might explain why I havnt noticed this problem. . 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... > > 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 > > -- > > gentoo-user@gentoo.org mailing list > -- gentoo-user@gentoo.org mailing list
