Re: [css-d] Floats problem (Firefox/Win)

[Roy Schestowitz <r@xxxxxxxxxxxxxxx>]

_____/ On Fri 04 Nov 2005 15:39:57 GMT, [ross] wrote : \_____

> ----- Original Message -----
> From: "Mikhail Bozgounov"
> To: <css-d@xxxxxxxxxxxxxxxxxxxxx>
> Sent: Friday, November 04, 2005 2:05 PM
> Subject: [css-d] Floats problem (Firefox/Win)
>
>
> > Here's the problem.
> >
> > Load the following page:
> > http://bluelink.net
> >
> > Scroll to the bottom (using FireFox) to see the following "bug":
> > http://bluelink.net/michel/screenshots/20051104_bluelink_ff_scroller_problem.jpg
> >
> > You can see the scroller ("pages 1, 2, 3, ... NEXT") to overlap the last
> > news
> > items in the page.
> >
> > *IF* you reload the page (just hit F5 to see), the problem DISAPPERS.
> >
> > Load it again (close browser, re-open), and here's the problem again...
> >
> > I suppose, it's *NOT* a bug, but a mistake in my CSS code (to be more
> > correct, a
> > mistake in the code of the developer /before me/, who created the current
> > html+css re-design...
> >
> > Anyway...
> >
> > I am stuck... I do not understand, why this DIV with the page numbers in
> > it
> > OVERLAPS the last news item...
> >
> > The css is at http://bluelink.net/master.css.
> >
> > All of the NEWS divs (which the scroller overlaps) are FLOATED, so to
> > contain
> > the image in them without a following clear (when a small image is present
> > in
> > the news div.)
> >
> > Any ideas welcome...
> >
> >
> > Michel
> >
> > PS This website works with rather "antique" CMS system, parts of which are
> > controlled with much difficulty... So *MOST* of the mistakes you'll see
> > when
> > validating, are caused by the "&" not encoded properly (&amp;) by the
> > CMS -
> > something which I cannot resolve...
>
> What version are you ruuning. This is similar to a problem I had with the
> older versions of FF when you resize the pages.
>
> Looks good on 1.5 beta 2.
>
> R.

I checked it yesterday as well (Firefox 1.0.x on Linux) and repeatedly 
failed to
reproduce the error. Maybe it is good news nonetheless. The error 
appears not to
affect all. Have you tried similar tests with Firefox on other 
machines? If not,
that would be my suggestions.

Best regards,

Roy

--
Roy S. Schestowitz
http://Schestowitz.com