Lst Recv wrote: >Georg sent me this private reply. For the benefit of the list, I >asked his permission to repost it to the list. > >(BEGIN:) >Opera _can_ float elements at the same level as non-floating elements - >even when a non-floating element comes first in the source-code. Other >browsers will drop the float below the non-floating element in such >cases. Nothing wrong the behavior for any of the browsers, but Opera's >way is actually a bit "unusual". > >
A clarification of this: Opera is wrong here. A float should not appear any further up the page than the non-floating stuff that precedes it. Since the second item is further down the page when it is unfloated, it makes sense that when you float it right it just moves to the right, doesn't move up to be on the same line as the previous element. If you want them to be on the same line without floating the first one left, you would need to switch their order -- the right floated one would come first, then the non-floated one. Also, earlier in the thread it was suggested that you remove the display: block declaration from your floats and use display: inline instead. This is not necessary. Floats are by their very nature block, and telling them to be inline doesn't change anything -- except for IE, where it can sometimes fix bugs. However, I wouldn't put inline on them unless you need to -- keep it simple until IE forces you to do otherwise. In general, you never need to declare a display value for floats. Zoe -- Zoe M. Gillenwater Design Services Manager UNC Highway Safety Research Center http://www.hsrc.unc.edu ______________________________________________________________________ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
