As a temporary and far from perfect workaround I added 1px to the width of the .container and .span-24 classes to my website. I works now, as long as I don't put smaller colums in a .span-2 to .span-23 classes. When I subdivide the container and .span-24 it works. I can't add pixels to the other classes, as everything would break.
Zooming out in Firefox now works at zoom level -1, If I go to zoom level -4, it has the same problem. But, I guess nobody uses zoom level -4. Found a related problem on StackOverflow: http://stackoverflow.com/questions/1274151/how-to-prevent-the-floating-layout-wrapping-when-firefox-zoom-is-reduced It shows that the problem is general, using floats with a border, and filling up the width completely from the wrapping div. So, not a blueprint itself problem. Would be nice though if Blueprint could offer a workaround. The post talks about using border-box as box-model. I tried a bit, but the padding is different, I would require quite a lot of rewrite in Blueprint and may have other disadvantages. On Dec 14, 6:00 pm, Michael Torfs <[email protected]> wrote: > Working on a website a friend of mine always had a problem with my > website. Some div's that I placed next to each other, he saw on 2 > lines (the last div moved to a new line). It was very frustrating, > until today I found out that his Firefox was on zoom level 90%, my > friend prefers it that way to see more on the screen. I noticed that > it is a problem with most Blueprint layouts. > > Here are the steps to reproduce the problem. I'm using Firefox 3.5.3 > on a Windows 7 machine. > > 1. > Make sure your zoom level is 100%, (CTRL-0) > > 2. > Open the grid demo page of > Blueprint:http://www.blueprintcss.org/tests/parts/grid.html > > 3. > Zoom out 1 level (I don't see it, but I assume it is to 90%) > > You will notice now that the second large span-12 parapgraphe moved to > a new line under the first span-12. > > I think it is a problem that blueprint fills every pixel in the width. > By zomming out, the firefox engine (is it Webkit?) recalculates > everything, I think there 90% of of everything rounded to pixels might > give the problem. Maybe the right-margin of first 'span-12 border' is > the problem. A 1px border probably stays 1 (rounded up) and might > cause that the recalculated total of 90% is 1px to much, causing the > second span-12 div to drop to a new line. If you can follow me, this > is just what I think. > > Anybody knows if this could be the reason, or if something else is the > problem? And more important, anybody has a solution? > > Michael -- You received this message because you are subscribed to the Google Groups "Blueprint CSS" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/blueprintcss?hl=en.
