Note that there are some explanatory texts on larger screens.

plurals
  1. POCSS clearfix problem with Firefox 2 and SeaMonkey
    primarykey
    data
    text
    <p>I am using <a href="http://www.yaml.de/en" rel="nofollow noreferrer">yaml</a> for layout and famous <a href="http://www.webtoolkit.info/css-clearfix.html" rel="nofollow noreferrer">clearfix css</a> to make sure container with floats get extended. </p> <p>Everything works fine with Firefox 3, IE6, IE7, IE8, Opera 9 and Google Chrome, but I have issue with Firefox 1, Firefox 2 and SeaMonkey. The problem is that clearfix container gets extended too much, as you can see on the website:</p> <p><a href="http://www.slagalica.tv/game/mojbroj" rel="nofollow noreferrer"><a href="http://www.slagalica.tv/game/mojbroj" rel="nofollow noreferrer">http://www.slagalica.tv/game/mojbroj</a></a></p> <p>Here are screenshots of <a href="http://www.slagalica.tv/firefox2.jpg" rel="nofollow noreferrer">Firefox 2</a> and <a href="http://www.slagalica.tv/firefox3.jpg" rel="nofollow noreferrer">Firefox 3</a> rendering.</p> <p><strong>Update:</strong> <a href="http://browsershots.org/screenshots/c50f599e3b570deca33f1a0d75379251/" rel="nofollow noreferrer">Screenshots on BrowserShots.org</a></p> <p>Unfortunately, stats show that more than 10% of my visitors are using FF2, so I cannot simply ignore the problem. I tried removing or tweaking some parts of clearfix CSS, but no matter what I do, the timer DIV (green) is separated by a large margin from the rest of the page.</p> <p>Does anyone have an idea how to solve this?</p> <p>Update2: I finally gave up and put TABLE tag and solved the issue in few minutes. So, don't try to look into HTML source - problem is not evident anymore.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload