Able to reproduce this issue on Windows-10, Mac OS 10.12.5 and Ubuntu 14.04 using chrome latest stable #59.0.3071.115 by following steps mentioned in the original comment. Observed table header overlaps with row content.

ncharrois@ Not sure is this issue is specific to chrome, Observing the same issue on Firefox as well, Could you please confirm ?

Thanks!

Hi brajkumar, thanks for your response.

I did make sure to test in Firefox before making this post and I'm not able to reproduce generating a PDF with the same steps (I've attached the Firefox pdf below, generated from 54 latest).

I've also attached the one generated by Safari, although it appears to have different issue where the PDF header does not repeat at all.

Please let me know if there's anything else I can help with. 

Deleted: firefox.pdf 42.9 KB

firefox.pdf 42.9 KB Download

Deleted: safari.pdf 39.5 KB

safari.pdf 39.5 KB Download

Thank you for providing more feedback. Adding requester "brajkumar@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Tested the  issue #59 .0.3071.115 on Mac 10.12.5 and was unable to reproduce the issue as per the steps mentioned comment #0.

Able to reproduce the  issue #59 .0.3071.115 on Ubuntu 14.04. Find the screenshot.

@ncharrois: Could you please find the attached screen cast and confirm Is that issue with Mac os or any?

Thanks!!

Deleted: Jul 21 2017 2-54 PM.webm 22.4 MB

Jul 21 2017 2-54 PM.webm 22.4 MB Download

Deleted: Screen Shot 2017-07-21 at 2.55.40 PM.png 74.2 KB

	Screen Shot 2017-07-21 at 2.55.40 PM.png 74.2 KB View Download

Hi @sandeepkumars, your screencast does not complete step #4. 

Presumably you are trying to demonstrate that this is an issue with the operating system and not Chrome? I am skeptical of this as other browsers don't have this issue (Firefox, Safari).

As mention in my original bug report, the bug occurs at the time of PDF generation, not print preview.

Thank you for providing more feedback. Adding requester "sandeepkumars@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Can some one from PDF team please look into this issue.

Thanks!!

halcanary@ is this something from the Skia side?

I'm not seeing this on Windows, Mac, or Linux with 59.0.3071.115. Here's a sample table.pdf from "Save As PDF" on Linux. Did I do something wrong while trying to reproduce this bug?

Also, can you try Chrome Canary and see the bug still happens there for you?

Deleted: table_linux.pdf 71.2 KB

table_linux.pdf 71.2 KB Download

This was reproducing for me on M59 Chrome for Linux, but is no longer reproducing for me on 60.0.3112.78. I was not able to reproduce on Mac with 59.0.3071.115. I suspect that this was fixed by a change in M59. Unless someone can reproduce this for M60 I recommend closing this bug.

rharrison: If you can repro with M59 locally, can you try:

tools/bisect-builds.py -a linux64 -g 464641 -b 474897 --use-local-cache --verify-range

in a Chromium checkout and see if you can figure out what fixed it?

Hi guys, I can confirm this is fixed in Chrome 60 on OSX using the original steps to reproduce. Will confirm with Windows asap.

Would also like to know what fixed it as I'm trying to ultimately have this fix backported to a library we're using that involves Qt Engine.

Thanks a lot guys

This issue hasn't being fixed. Checkout this screenshot https://cl.ly/411B3C0h0p2C of last page "table.pdf" file. Using Version 61.0.3163.100 (Official Build) (64-bit) on OSX. 

Can confirm with Comment 17. Using the original steps to reproduce looks like the bug has regressed since 60.

High Sierra 10.13
Chrome Version 61.0.3163.100 (Official Build) (64-bit)


Also I think this issue was mistakenly marked as 'Wont fix'.

Well, in comment 15, you said it doesn't happen anymore, so at that point, what more can we do at that point to fix the bug?

If the bug was fixed in Chrome 60 the issue should have been marked as "Fixed".  

And seeing as multiple people have confirmed the bug, marking it "Wont fix" doesn't really make sense, does it?

This is a common point of confusion. When we didn't actually take any action to fix the bug, then we didn't fix it, did we? Thus the resoltion is WontFix. If someone actually did something, then we mark it fixed.

As I said in comment 10, I can't reproduce this, so I can't even confirm that this was broken in M59, fixed in M60, and broken again in M61. For all we know, the bug may be flaky in some way, and you got luck with M60. Thus the bug is currently open again, and we'll try to figure it out.

This is a bug with PDF generation so removing the Internals>Plugin>PDF label. Assigning to halcanary@ to take a look.

I am not able to reproduce at this time with Chrome 67.0.3381.0 (Official Build) dev (64-bit) on Linux.

Tested on latest Chrome #66.0.3359.117 and Canary #68.0.3408.0 and was not able to reproduce the issue. Attached the PDF file generated.

ncharrois@ -- Could you please verify on latest builds and let us know your observations.

Thanks!

Deleted: table.pdf 173 KB

table.pdf 173 KB Download

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

pnangunoori@ Yes, I can confirm using the original steps to reproduce that this has been fixed. 

Thanks for your efforts and everybody who participated in helping reproduce the bug.

Deleted: table.html.pdf 34.5 KB

table.html.pdf 34.5 KB Download

Closing this issue as the issue seems to be fixed.

Thanks!