View Single Post
Old 09-12-2014, 01:48 AM   #86
dgatwood
Curmudgeon
dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.
 
dgatwood's Avatar
 
Posts: 629
Karma: 1623086
Join Date: Jan 2012
Device: iPad, iPhone, Nook Simple Touch
Quote:
Originally Posted by DaleDe View Post
I think it could be argued that this is the correct behavior. I don't think this is defined in the spec but if the figure is after the first character then floating it left on the first line would change the order of the information by placing the figure visually ahead of the character. I think the behavior of floating it left after the first character is correct. Which readers do it differently?
Hopefully all of them. The only situation where a float is allowed to move to a new line, AFAIK, is when you have too many of them to fit on a single line.

For sure, WebKit floats them both correctly (left or right) on the first line, so iBooks, Kindle (KF8), and most other non-ADE readers should float them correctly.

With that said, check your margins to ensure that you don't have a big top margin (which could push it down), and be sure to set that span to be a block element. Floating an inline element is nonsensical, and just about any random interpretation of such invalid CSS could probably be considered correct.
dgatwood is offline   Reply With Quote