Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 356229

Summary:	no pagebreaks in report with a text element with a large html as content type
Product:	z_Archived	Reporter:	eminaguil
Component:	BIRT	Assignee:	Birt-ReportEngine-inbox <Birt-ReportEngine-inbox>
Status:	NEW ---	QA Contact:	Hao Zhou <hao.zhou>
Severity:	major
Priority:	P3	CC:	bluesoldier, h.vonbargen, rgosling
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	All
Whiteboard:

Description eminaguil

2011-08-30 12:58:52 EDT

Build Identifier: 3.7.0

In a report with records in a table, if there is an element in a detail row and this is a text element with html as content type. And the value of the record takes more than one page for example two, when you see the preview you see the same report as page 1 and page 2, and when you print the report as pdf, you got 4 pages, the report in page 1 and 2 and then it repeats.

If the html in the report has n pages in the preview it shows n pages of the same report and in pdf/word it shows n*n pages.

I´m using Birt 3.7 on apache-tomcat-7.0.19, same problem with 2.6 on apache-tomcat-7.0.6 . I've tested in FF3 up to FF6, IE8 and chrome 12 in Windows Sever 2003, WinXP and WinVista

Reproducible: Always

Steps to Reproduce:
1. Use a recorset with a field with a large html value
2. Create the report and insert a table
3. Create the biding to the the field
4. Insert a text element in a detaill row with the context type as html and add the biding to the field as value(<VALUE-OF  format="HTML">row["field_name"]</VALUE-OF>) 
5. Save the report and use the ReportViewerExample from the birt-runtime to view it, then print as pdf or export to pdf, word

Comment 1 Rob Gosling

2013-11-05 18:27:04 EST

I am experiencing the same issue.  Is there likely to be any action taken to resolve this bug?

Comment 2 Rob Gosling

2013-11-05 18:32:40 EST

(In reply to Rob Gosling from comment #1)
> I am experiencing the same issue.  Is there likely to be any action taken to
> resolve this bug?

Just thought I'd add that I only seem to encounter this with a Fixed Layout mode.  Auto layout from my testing works fine.  But I require Fixed layout for something else.