Yea you're right. It's def. the specifity. I just reproduced something similar in another scenario. It can be solved with assigning a span-x class.
[code] <div class="span-24"> <div class="span-23 last push-1">Test #1</div> <!-- [1]--> <div class="span-10 push-1">Test #2</div><!-- [2] --> </div> [1] No problem. The span pushes it back. [2] Problem. If assigning no span-x , the content defines the width and everything get's floated right. If you assign a span-x that's not span-24 minus push-1 = span-23 last it starts on the right side. As far as i have thought now: a) prepend-x => pushes content inside element to the right b) append-x => make space on the right side oft he content (still left alligned) c) push-x => pushes element to the right (in theory) d) pull-x => pulls element to the left When looking at the push-x behavior: It's not that bad as it is now, because sometimes you need to change the direction from ltr to rtl. IMHO: We ain't got the wrong behavior. We are just missing one thing: either a real "push" behavior or the current "push" (from right) behavior. What i think could be done to make bp better: 1) move "push" classes on top of "span" classes and rename them "push-l-x". 2) make "push-r-x" classes where the "push" is now sitting. What i don't know so far: A) Could we need "pull-l-x" and "pull-r-x" classes too? I have never needed them so far, but maybe someone other has. Wish you best. -K. -----Ursprüngliche Nachricht----- Von: [email protected] [mailto:[email protected]] Im Auftrag von garethjmsaunders Gesendet: Dienstag, 06. Juli 2010 22:01 An: Blueprint CSS Betreff: [BP #4005] Re: Query about alignment of push-x classes Okay, so I swapped the order. Originally the code read: <div class="span-1 push-1"><p>1</p></div> but then I swapped them around: <div class="push-1 span-1"><p>1</p></div> and I get exactly the same result, because it's not to do with the order of the classes in the HTML mark-up, it's to do with the order of the CSS cascade, because, and I quote Eric Meyer, "the later a declaration appears in a style sheet or a document, the more weight it is given." (CSS Pocket Guide, Third edition, O'Reilly, 2008, p. 9) So, because .push-1, .push-2, .push-3, .push-4, .push-5, .push-6, .push-7, .push-8, .push-9, .push-10, .push-11, .push-12, .push-13, .push-14, .push-15, .push-16, .push-17, .push-18, .push-19, .push-20, .push-21, .push-22, .push-23, .push-24 {float:right;position:relative;} comes AFTER .column, .span-1, .span-2, .span-3, .span-4, .span-5, .span-6, .span-7, .span-8, .span-9, .span-10, .span-11, .span-12, .span-13, .span-14, .span-15, .span-16, .span-17, .span-18, .span-19, .span-20, .span-21, .span-22, .span-23, .span-24 {float:left;margin-right:10px;} the float: right takes precedence. My underlying point is that I don't think push-x should have a "float: right" declaration at all. It seems to make far more sense to me for it to be "float: left". And that's what I'm really wanting folks opinions about. Ticket #114 on the Lighthouseapp bug tracker "Push/pull with Blueprint VS. 960.gs" is interesting: http://blueprintcss.lighthouseapp.com/projects/15318/tickets/114-pushpull-wi th-blueprint-vs-960gs Hasse writes, "On the 960.gs website it's stated on the front page, under Source Order that "By utilizing the push_XX and pull_XX classes, elements can be rearranged, independent of the order in which they appear in the markup ... I was simply wondering - why isn't this simple and neat feature not available in Blueprint?" It would appear to me, after initial tests, that this is possible if the push-x classes were set to "float: left;". Gareth On Jul 6, 2:22 pm, "24/7" <[email protected]> wrote: > Normally such a behavoir (i see it but can't replicate it on my own > test-page) comes from serving the classes in the wrong order. Than you can > expect that they are overriding each other, so only float: right will get > applied. When i look at my own pages, where i use the same doctype and same > bp-stylesheets, i get (in firebug) first my span class and then my > push-class, so the push float: right get's overridden by my span float: left > > I'm sorry, that i can't help you more, but maybe you will find the answer in > the loading order... > > -----Ursprüngliche Nachricht----- > Von: [email protected] [mailto:[email protected]] Im > Auftrag von garethjmsaunders > Gesendet: Dienstag, 06. Juli 2010 08:31 > An: Blueprint CSS > Betreff: [BP #4002] Re: Query about alignment of push-x classes > > To demonstrate further what I mean, I've created the following example > page: > > http://www.garethjmsaunders.co.uk/blueprint/push/ > > Gareth > > -- > 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 athttp://groups.google.com/group/blueprintcss?hl=en. -- 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. -- 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.
