Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reporting - Sometimes an unwanted page break appears at the beginning of the Questionnaires #546

Open
jocelyncardinal opened this issue May 22, 2019 · 10 comments
Assignees

Comments

@jocelyncardinal
Copy link

Describe the bug
Reporting - Sometimes an unwanted page break appears at the beginning of the Questionnaires

Capture d’écran, le 2019-05-14 à 11.11.34.png

To Reproduce
It happen something but I don't know yet how to reproduce it. More to come ...

@iamkinetic
Copy link
Member

Well since page break is not an html thing and we never add any page break, i would think the Html to Pdf tools is trying to keep the table's row on one page.

@iamkinetic
Copy link
Member

Well it was a known issue in some earlier version, i don't know which version we are currently using.

https://stackoverflow.com/questions/13516534/how-to-avoid-page-break-inside-table-row-for-wkhtmltopdf

There's some css stuff I could try.

@iamkinetic
Copy link
Member

css trick (add thead and tbody) :

tr, td div, th div
    page-break-inside: avoid;
}

@jocelyncardinal
Copy link
Author

WOW!

@iamkinetic
Copy link
Member

Je vais injecter ce css à la création du document, ça devrait régler le problème.

@iamkinetic iamkinetic added this to the 1.7.X milestone May 22, 2019
@Jeepsboucher Jeepsboucher self-assigned this May 27, 2019
@iamkinetic
Copy link
Member

@Jeepsboucher SVP indiquer ce qui fait que ce point est bloqué et ce que ça prend pour le débloquer.

@iamkinetic iamkinetic removed this from the 1.7.X milestone May 30, 2019
@Jeepsboucher
Copy link

@iamkinetic J'ai essayer le code que tu avais mis plus haut, cela n'a pas fonctionné. J'ai essayer de trouver une autre solution, mais au final rien n'a marché. De plus, certain rapports n'ont pas le problème.

@jocelyncardinal
Copy link
Author

Effectivement, le probleme n'arrive pas sur tout les rapports mais de memoire il me semble que ca arrive quand meme assez régulièrement. Est-ce que ca dépend des champs (questions) qui ont été rempli ou laissé vide???

@iamkinetic
Copy link
Member

Nous n'avons pas réussi à régler ce problème et nous le mettons de côté pour l'instant.

@jocelyncardinal
Copy link
Author

jocelyncardinal commented Jun 4, 2019 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants