Hi Daniel! Many many thanks for your quick reply and pro help! I really appreciate it. :)
On Fri, May 11, 2012 at 12:51 PM, Venditelli, Daniel - Web Development Administrator <[email protected]> wrote: > Assuming equal width columns, this means initially the viewer sees > [1][2][3][4] and as the window narrows, 4 drops first, then 3, then 2 as > below: > [1][2][3] > [4] > then > [1][2] > [3][4] > then > [1] > [2] > [3] > [4] Exactly! :) Thanks so much for illustrating... I was not sure of the best way to include a visual with my first message; what you have above is exactly the current functionality. > To reverse that dropping order, the easiest solution would be to do the > following: Thanks for the examples. You've really made the solutions clear and understandable. > Are you avoiding float:right to preserve the initial order of the > content OR to avoid having all of the content shift to the right side of > the page? Good question! The latter. The shifting is not what I am worried about. I would prefer to not touch the source order and I would like to keep the visual order. I don't normally use float:right for my floated layouts... I was hoping that I could just add a class of "reverse" (for example's sake) to the parent container and have that class apply a float:right (overriding my float:left) to the columns; I quickly discovered (as you pointed out) that the source order needs to (also) be reversed in order to maintain the "visual" ordering. Basically, I want to make it easy to control which columns show on top of other columns; re-arranging the source code, and using float:right, would make this task a bit more tricky (and possibly not worth it in terms of the templating system and environment I'm working with). > If you are merely trying to preserve that initial content order and the > drop order, I think Example B will work for you (it's possible to Thanks again! I'll experiment with your ideas/suggestions. > the order of the source code will not match the display order for screen > readers and the like which is something you should be aware of. Good point. > I now it's not a necessarily a solution, but hopefully, it clarifies the > question enough to spark a thought for you (or for others) For sure! Your reply has been very helpful! Thank you so much for taking the time to respond, I really appreciate it. :) Have a nice day! Cheers, M ______________________________________________________________________ css-discuss [[email protected]] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
