Bugzilla – Full Text Bug Listing
| Summary: | [Improve Page Break Management] "PageBreak avoid" leads to data mixing in sub-subreport | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Christina Stellmach <christina.stellmach> | ||||||
| Component: | BIRT | Assignee: | Birt-ReportDesigner <Birt-ReportDesigner-inbox> | ||||||
| Status: | VERIFIED FIXED | QA Contact: | Xiaodan Wang <xwang> | ||||||
| Severity: | critical | ||||||||
| Priority: | P3 | CC: | bas, bluesoldier, christophe.garabedian, contact, enricomilanese, hustlg, wenfeng.fwd, wyan, xwang, zqian | ||||||
| Version: | 2.2.0 | Keywords: | plan | ||||||
| Target Milestone: | 2.5.0 M7 | ||||||||
| Hardware: | PC | ||||||||
| OS: | Windows XP | ||||||||
| Whiteboard: | Autoed,G | ||||||||
| Attachments: |
|
||||||||
|
Description
Christina Stellmach
Created attachment 78529 [details]
zip containing report project with example
Hi, Christina Do you mean some table headers were repeated twice at wrong place? If so, we have fixed the problem before. Pls download our new build for a try. (In reply to comment #2) > Hi, Christina > Do you mean some table headers were repeated twice at wrong place? > If so, we have fixed the problem before. Pls download our new build for a try. No, its much more critical. See the attached example: On pageBreakAvoid.pdf page 9 and pageBreakAuto.pdf page 6 the result starts to differ in content. In pageBreakAuto.pdf the content is correct, in pageBreakAvoid.pdf the content is wrong !!! Hi, I'm experiencing exactly the same problem (running BIRT 2.2.0). I have a Table Group with a repeatable header. When I set "Page break inside = avoid", the data comes out all wrong in the PDF report (but not in the preview). If the User of our Reporting environment creates a report, the pdf Output is a document which will be released. THIS is "the report", not the html view on the screen. I do not understand, why you reduce the Priority of this bug. Do I have to explain the criticality of data mixing in aircraft industrie ? We have disabled "PageBreak avoid" from BIRT 2.2, and will support it in the future. Currently, "PageBreak avoid" does not take effect and does not lead to data mixing. defer to future and should be resolved with the page number/page model/page event together. Hi guys :) Is 2.5.0M5 still the actual target? Is the fix already available in HEAD? ping? The issue is caused by page-break-avoid, The implementation of page-break-avoid had been removed since 2.3.1. So the issue does not exist, but page-break-avoid is not supported yet. Thanks for answer!
In fact what I meant was: when will page break avoid be supported again?
Because we need a solution to avoid page break in the middle of a group in cross tabs.
For example
X Y Z
2008 Q1 a b c
Q2 d e f
Q3 g h i
Q4 j k l
2009 Q1 a b c
Q2 d e f
Q3 g h i
Q4 j k l
Can be rendered this way
X Y Z
2008 Q1 a b c
Q2 d e f
Q3 g h i
-------------- > page break
X Y Z
Q4 j k l
2009 Q1 a b c
Q2 d e f
Q3 g h i
Q4 j k l
and this is bad :(
The page break "auto" at "quarter" level should be settable to "avoid"...
Or perhaps am I just not aware of an existing workaround for that kind of problem?
need more time to resolve those issues. Support page-break avoid. Verified in build (2.5.0.v20090309-0630). (In reply to comment #13) > Support page-break avoid. > Even if it is now possible to use 'avoid' values in the "page break" settings of cross tab groups, it doesn't seem to have any effect... Am I missing something? Cheers (In reply to comment #15) > Am I missing something? Well, it is perhaps bug 183056? If it is, will a fix be done for the 2.5 version? Thanks again! (In reply to comment #16) > (In reply to comment #15) > > Am I missing something? > Well, it is perhaps bug 183056? > If it is, will a fix be done for the 2.5 version? > Thanks again! 183056 does not seem to be the same issue. Reopen this bug to verify that page break avoid is supported for Xtab Row dimension levels (groups). Reassign to xtab team to support page-break-avoid first. page-break-avoid has worked for table, and bug 268290 has already been submitted for the support of crosstab page-break-avoid. The Crosstab "page break avoid" support is traced by bug 268290. I'm marking this bug as fixed as it's originally for Table and Grid. Created attachment 131753 [details]
2 samples with problems
Hi guys,
The "Pagebreak avoid" functionality has been fixed (Verified in build 2.5.0v20090410), but I found some other regressions (See the attached file "2 samples with problems.zip") :
Sample 1 :
- At the bottom of page 1, the horizontal line is not aligned.
- The page 3 should not exist.
Sample 2 :
- At the bottom of page 1, the line is missing.
Thanks in advance.
Cheers.
(In reply to comment #21) > Created an attachment (id=131753) [details] > 2 samples with problems > > Hi guys, > > The "Pagebreak avoid" functionality has been fixed (Verified in build > 2.5.0v20090410), but I found some other regressions (See the attached file "2 > samples with problems.zip") : > > Sample 1 : > - At the bottom of page 1, the horizontal line is not aligned. > - The page 3 should not exist. > > Sample 2 : > - At the bottom of page 1, the line is missing. > > Thanks in advance. > Cheers. > Christophe, For Sample 1: - At the bottom of page 1, the horizontal line is not aligned. Open a new bug 272466 for this. - The page 3 should not exist. The third page is generated because you set page-break-after: always to the group, and if you remove the setting, the group "ESCADRON : Saint-Dizier" will be drawn in the second page. For Sample 2 : - At the bottom of page 1, the line is missing. I run the report in build (2.5.0.v20090416-0630) and it can not be reproduced again. Though the border is drawn, the same thing happens as Sample 1 that at the bottom of page 1, the horizontal line is not aligned which can be tracked by bug 272466. Thanks Set this bug as Verified. You're right. I'll track the bug 272466. I hope it will be fixed as soon as possible. Thanks in advance. Cheers. |