| Summary: | Story does not handle HTML "page-break-after" correctly. | ||
|---|---|---|---|
| Product: | MuPDF | Reporter: | Julian Smith <julian.smith> |
| Component: | mupdf | Assignee: | Robin Watts <robin.watts> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | robin.watts |
| Priority: | P2 | ||
| Version: | master | ||
| Hardware: | PC | ||
| OS: | Windows 10 | ||
| Customer: | Word Size: | --- | |
| Attachments: | Check Story with page-break-after. | ||
Fixed in: commit a2d0c1206963939a3cf76abcb958b2cd7d771dcb Author: Robin Watts <Robin.Watts@artifex.com> Date: Wed Nov 15 18:07:15 2023 +0000 Bug 707323: Fix page-breaks with restarting layout. Page breaks were terminating the layout process in unexpected ways. Also fix page-break-after with tables. |
Created attachment 25012 [details] Check Story with page-break-after. fz_place_story() gets confused if html contains 'page-break-after'. It does not producing a new page, and subsequent text does not appear when the generated PDF is viewed. [But the subsequent text is present in the generated PDF and can be found using stext.] Attached test checks that generated PDF has two pages, and assert-fails.