Right floating elements that are bigger than their parent element should touch the right edge of the parent and stick out the left, I would think. It's not all that serious. See the last 2 tests in the above URL. (Actually the forty-third and forty-fourth - I may add more.)

I landed a fix for this on monday; note that you won't get a horizontal scrollbar for things sticking out the left edge.

Your fix changed things so that the text in the last paragraph in the above page doesn't flow below the float anymore. It ends up above it. It should work just like the next-to-last case.

This looks fixed. However, I really think you ought to provide a scrollbar for left/top overflow. This is especially serious for RTL text. The initial position should still be (0,0). I guess I should file that as a separate RFE...

Has been fixed, probably by recent incremental reflow w/floaters bug fixes.

Using 10/20 app, verified fixed.

I'm reopening this because the bug described in my 04/22 comment has returned. I'll try and get you a simplified test case...

The problem is actually incremental. It goes away on a resize reflow. Marking {inc}.

I can't get a good test case because this seems to be highly dependent on the other contents of the file - probably because the incremental reflow units are now based on the size of the chunks handled by the networking code. The problem is in the second to last test case of the above URL. I imagine it may not be reproducable anymore if the network code or content sink changes.

Updating to default Layout Assignee...kipp no longer with us :-(

Why are you re-reassing layout bugs? Do NOT touch layout bugs. The bugs are assigned to Kipp so they can stay neatly organized until we have a new owner for the block/inline code.

Migrating from {css1} to css1 keyword. The {css1}, {css2}, {css3} and {css-moz} radars should now be considered deprecated in favour of keywords. I am *really* sorry about the spam...

mine! mine mine mine! all mine! whoo-hoo!

moving all buster m15 bugs to m16.

redistributing bugs across future milestones, sorry for the spam

As per meeting with ChrisD today, taking QA.

The bug seems to have gone. Marking WORKSFORME, but David could you check this again? Your comments mention 44 tests on that page but the last two are numbered in the twenties so I don't know if the bug really is fixed...