search

amitdivya / dompdf

Automatically exported from code.google.com/p/dompdf
0 stars 0 forks source link

block element nested in inline element breaks page reflow #116

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.If my pdf data exceeds 1 page
2.
3.

What is the expected output? What do you see instead?
The expected output is that the data should go on next page in pdf. All of
the data that exceeds one page is overlapped on the start of pdf.

What version of the product are you using? On what operating system?
I am using 0-6-0_alpha2

Please provide any additional information below.

I am attaching two files that are being generated. One of them is defective
in which the data is more than one page and it gets overlapped. The another
one is lesser than 1 page and it is perfectly generated

Original issue reported on code.google.com by emphatic...@gmail.com on 18 Jan 2010 at 3:12

Attachments:

GoogleCodeExporter commented 9 years ago 
I believe you are probably running into the problem described by Issue 70. Do 
you have any table rows that 
contain no text?

Original comment by eclecticgeek on 18 Jan 2010 at 6:30

GoogleCodeExporter commented 9 years ago 
There is no table rows without text. All rows contain some kind of data in it.

Original comment by emphatic...@gmail.com on 18 Jan 2010 at 7:19

GoogleCodeExporter commented 9 years ago 
Can you post a sample of the HTML that's giving you problems? It can be hard to 
determine what's going on 
without the source document.

Original comment by eclecticgeek on 18 Jan 2010 at 10:22

GoogleCodeExporter commented 9 years ago 
Has there been a resolution to this?

Original comment by mattconn...@gmail.com on 27 Dec 2010 at 4:56

GoogleCodeExporter commented 9 years ago 
A sample HTML document that exhibits the problem was never posted. Without this 
we do not have a good way of identifying what is causing the problem. If you 
are experiencing a similar issue please feel free to post a sample we can test 
against.

Original comment by eclecticgeek on 27 Dec 2010 at 6:49

GoogleCodeExporter commented 9 years ago 
Here is some html that isn't working for me

Original comment by mattconn...@gmail.com on 7 Jan 2011 at 3:37

Attachments:

GoogleCodeExporter commented 9 years ago 
I have updated to trunk (currently 345) with no luck

Original comment by mattconn...@gmail.com on 7 Jan 2011 at 4:44

GoogleCodeExporter commented 9 years ago 
Your problem is due to structural errors in your HTML, namely you have block 
elements inside inline elements. This is confusing dompdf when it reaches the 
end of a page and it loses track of the document layout.

To address the issue in your document, your span tags should be changed to div 
tags. It's always good practice to ensure that your HTML is valid before 
passing it to dompdf. But we will address the issue at some point in the future.

Original comment by eclecticgeek on 7 Jan 2011 at 6:22

GoogleCodeExporter commented 9 years ago

Original comment by eclecticgeek on 7 Jan 2011 at 6:22

GoogleCodeExporter commented 9 years ago 
That makes perfect sense. I replaced all the spans with divs, and that helped 
out a bit, instead of one page, I now have three. The first two are good but 
now the third page is jubgle gook.

Thanks for the second eyes and support.

Original comment by mattconn...@gmail.com on 9 Jan 2011 at 9:25

Attachments:

GoogleCodeExporter commented 9 years ago 
I also replaced the p tags with div tags and that solved the output problem. It 
would be nice to solve the problems though.

Original comment by mattconn...@gmail.com on 9 Jan 2011 at 10:15

GoogleCodeExporter commented 9 years ago 
You are correct. There does appear to be a propagation problem of the document 
structure on the third page.

If you go back to the beta 1 release the document renders correctly. We'll have 
to take a look and see where the latest code is breaking.

Original comment by eclecticgeek on 10 Jan 2011 at 7:59

GoogleCodeExporter commented 9 years ago

Original comment by eclecticgeek on 24 May 2013 at 3:00