|
Also note that a general use web browser like Firefox can not make any sort of assumptions about the content it handles. It must assume that a web developer will use floats everywhere, and they expect the browser to follow the CSS layout spec to the letter.
Therefore, implementing an algorithm like K&P, which may or may not be feasible to follow all the rules, would be opening up a huge can of worms that they probably don't want to deal with.
An ebook renderer I feel has a much narrower scope of the content it is expected to layout. One can make (some) assumptions about content. Also every ebook renderer has its quirks, so what's another reader that doesn't quite lay out a float in the exact manner that CSS says it should be, so long as it's close enough?
|