When a floating object is pushed to the next page, column or region as a result of either being unsplittable or because of a pagination strut, we need to recalculate its position. It may move to an area with more available width, below other floats, etc.,
Created attachment 108270 [details] Patch
Comment on attachment 108270 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=108270&action=review > Source/WebCore/rendering/RenderBlock.cpp:3272 > +LayoutPoint RenderBlock::computeLogicalLocationForFloat(FloatingObject* floatingObject, LayoutUnit floatLogicalTop, LayoutUnit leftOffset, LayoutUnit rightOffset, LayoutUnit floatLogicalWidth) Can this be a const member function? Can it take a const FloatingObject*? Is "location" specific enough in this function name? Should it say "top left" instead? It's confusing that you pass a value named floatLogicalTop into a function that is supposedly calculating that value for you. Is there a clearer way we can name the parameter that makes it clear what the caller has to do when calculating that value vs. what the function will do based on that value? > LayoutTests/ChangeLog:11 > + * fast/regions/webkit-flow-floats-inside-regions-bounds-expected.txt: Don't you need to update pixel results, too?
Fixed in r95724.