|
|
Rank: Advanced Member
Groups: Member
Joined: 7/14/2014
Posts: 40
|
I've noticed a problem with EO.Pdf (v5.0.87.2) with (I think) regards to CSS overflow property setting. In the PDF output some content is clipped whereas neither MSIE, Firefox, or Chrome clip the content. I sent an e-mail to support yesterday (Subject: Clipped Content in HTML to PDF output) regarding this and I'm just following up with a forum post today.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,196
|
Hi, We have looked into the file you sent to us. Please try to remove "overflow: HIDDEN" on the cells with rowSpan property and see if it corrects the problem for you. The root of the issue is our HTML engine can not properly handle overflow with rowSpan together. You can use the following HTML code to reproduce the problem:
Code: HTML/ASPX
<table>
<tr style="overflow: hidden">
<td rowspan="2">
A
</td>
<td>
B
</td>
</tr>
<tr style="overflow: hidden">
<td>
C
</td>
</tr>
</table>
Here cell A will be clipped because the first TR has "overflow:hidden", thus causes the HTML engine to think its boundary is restricts by the boundary of the first row without considering the fact that cell A expands to the second row as well. The work around is to remove the "overflow:hidden" attribute on the row before this problem can be permanently fixed. So you can try that in your HTML and see if it resolves the issue for you. Thanks!
|
|
Rank: Advanced Member
Groups: Member
Joined: 7/14/2014
Posts: 40
|
I will give that a try but it might impact the layout. Generally we don't have control over the HTML being submitted however in this particular case the HTML is generated internally so we could modify that process. Luckily I think that overflow is likely used very little in overall so hopefully only a small fraction of all documents would actually be impacted.
Are there any plans to address rowSpan + overflow?
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,196
|
Hi,
Certainly, the real question is not if, but when. Our HTML engine is based on WebKit so we would think this is an issue originates from WebKit but obviously has been fixed in newer branches. Our EO.WebBrowser uses Chrome's blink engine which is one of such newer branches. We are in the process of moving EO.Pdf to the newer blink engine but we do not have an ETA yet since its a rather complicated process. We expect these issues to be resolved when we switch to the new engine.
Thanks!
|
|
Rank: Advanced Member
Groups: Member
Joined: 7/14/2014
Posts: 40
|
Confirmed. Removing the overlap property from the elements has eliminated the clipping.
I'm aware of the work to move EO.Pdf from WebKit to Blink from other conversations via e-mail with Jack. Would be nice if there was an ETA for this but I understand that it's a very big undertaking. So you're fairly confident that the issue is in the WebKit engine and not in your PDF conversion codebase?
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,196
|
Hi,
Yes. We have debugged into WebKit code and traced this problem back there. In fact if you put the above HTML into a HTML file and then open it with Apple Safari you will see the same problem too.
Thanks!
|
|