Yet again I feel I must point out the flaws in the current fluid solution. I have already commented on a previous thread with the pertinent parts being:
The problem comes with each level deeper you go, the percentages are wrong. If on the first level I had a "span-12, span-6, span-6" the percentage equivalent would be "50% 25% 25%" If inside the span-12 you then broke it into "span-6, span-6" again, the span-6 would now need to be 50% If the span-6 was in a span-18 instead, it would need to be 33% Basically I would need to figure out the correct percentage of a span- # when it is inside any span-# that is larger then itself. When I move an additional level deeper, I would need to refigure yet again. As you can see this ends up with hundreds of permutations and that will naturally make the filesize grow significantly. I bounced this off of a few others and we couldn't find any way around it... so please call us on our stupidity if we are missing something. So, while the above can techincally be overcome, the filesize would be very prohibitive. ---- and then specific to the current implementation Thanks for the link. I was really excited as I saw it work until I looked a little closer. Unfortunately he did run into the issue I described above about it getting complicated as you move additional levels deeper. His large left column is a span-15. Lower in the page he shows a 50/50 split which you would think should be a span-7 and span-8 (yes, not really 50/50). He instead had to use a span-11 and span-12 to create the layout he wanted because those are the span-* selectors that have the 50%-ish width. So while yes, this got the job done... it's not the nice and easy blueprint we know and love as you need to continue to reference back to the CSS to see which span matches up with the percentage you want a given block to take. Props for getting that far and finding a way to make it work, and I guess it's a good thing to have in the back pocket, but not a silver bullet by any means as I can't just switch from fluid to fixed if I wanted. Copied from: http://groups.google.com/group/blueprintcss/browse_thread/thread/138dd9bcf2e679df/ Aaron On Oct 15, 6:20 am, Italo Maia <[EMAIL PROTECTED]> wrote: > I don't get it. What is the difference between liquid layout and > normal layout? They seem the same to me. > > On 14 out, 10:09, "Christian Montoya" <[EMAIL PROTECTED]> wrote: > > > On Tue, Oct 14, 2008 at 6:21 AM, jibbajabba <[EMAIL PROTECTED]> wrote: > > > > Design By Fire adds this file using conditional comments to fix IE6: > > > >http://www.designbyfire.com/liquid_blueprint/blueprint/lib/ie.css > > > > Has anyone had a look at that file and the IE fixes and determined if > > > it makes liquid layout bombproof? > > > Ah OK, it's the classic 3px float jog. That's a solid fix, except for > > being written as a hack. We could put that into the base ie6.css that > > Blueprint comes with since I'm sure it would prevent other float > > problems. > > > -- > > -- > > Christian Montoya > > christianmontoya.net --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
