Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
1.1, 2.0, 2.1
-
None
-
None
-
Windows 7
Description
In the attached examples more.fo and less.fo, page 1 has a content width of 5.5in, achieved with 1in page margins, and an extra 1in region-bdy margin-left.
In more.fo, the other pages have a content width of 6.5in, as they have a region-body margin-left of 0in. In less.fo, the other pages have a content width of 4.5in, as they have a region-body margin-left of 2in.
There's space at the bottom of page 1, but not enough for a scale-to-fit graphic. So the graphic gets bumped to page 2. The graphic correctly scales its width to fit the page 2. And it correctly scales its height in proportion to its width.
However, at the bottom of page 2, text either overflows to page 3 too late or too soon.
In more.fo, text at the bottom of page 2 overflows onto page 3 too late, running over the footer when it should get bumped to page 3. It appears that, for the purposes of determining if there is space left on the page, the height of the graphic is counted as if it had appeared on page 1, instead of the wider page 2.
In less.fo, the text at the bottom of page 2 overflows onto page 3 too soon, stopping well above the footer. Again, it appears, that for the purposes of determining if there is space left on the page, the height of the graphic is counted as if it had appeared on page 1, instead of the narrower page 2.