| Summary: | Birt does a Pagebreak if pageRange is set. | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | pp | ||||||||
| Component: | BIRT | Assignee: | Yu Chen <yChen> | ||||||||
| Status: | VERIFIED FIXED | QA Contact: | Xiaoying Gu <bluesoldier> | ||||||||
| Severity: | major | ||||||||||
| Priority: | P3 | CC: | bluesoldier, pp | ||||||||
| Version: | 2.6.1 | ||||||||||
| Target Milestone: | 3.7.0 M7 | ||||||||||
| Hardware: | PC | ||||||||||
| OS: | Windows 7 | ||||||||||
| Whiteboard: | Obsolete | ||||||||||
| Attachments: |
|
||||||||||
|
Description
pp
Created attachment 185337 [details]
An example of the bug
Created attachment 185341 [details]
The code that executes the report
Created attachment 185342 [details]
The report that shows the bug
I forgot to mention: I've played with scripting and found out, that the onPageBreak-event of a surrounding element (table-detail for example) is not fired before the page with the two rows. The content in first page is displayed 2 pages because the label in the first page is split into 2 page. User can avoid this problem by setting page range as "1-n". Anyway, since the report is fixed-layout, we can output the first page as what it is. Fixed. Verified in daily build 3.7.0.v201104050630 |