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

Column overflow with template MultiDefaultByColumn.pt #2

Open
grulisco opened this issue Apr 23, 2018 · 2 comments
Open

Column overflow with template MultiDefaultByColumn.pt #2

grulisco opened this issue Apr 23, 2018 · 2 comments

Comments

@grulisco
Copy link
Contributor

Steps to reproduce

  • Create a report over e.g. 10 ARs with same analyses services or profiles
  • Choose template MultiDefaultByColumn.pt

Current behavior

Result table shows only the first 5 ARs, the rest is lost.

Expected behavior

Results of all ARs should be displayed in separate table sections
following the setting "Maximum columns per results email" in Bika Setup/Result Reports
or create a new item in senaite publisher settings for this.

Screenshot (optional)

spectacle c18418

@ramonski ramonski added the bug label Apr 24, 2018
@ramonski
Copy link
Contributor

Thanks for reporting @grulisco.

Unfortunately Weasyprint does not support table cell splitting on horizontal overflow.

This leaves us with the following options:

  • smaller font for the whole table, so that more columns fit
  • word wrapping inside cells (so the ID breaks into multiple lines)
  • using horizontal orientation (then 8 columns fit)
  • using a higher paper format, e.g. A3
  • dropping the table and use <div class='col'> boxes instead

The last point should break the next box below, but I doubt that it will be easy to make the columns fit aligned below each other or with the same width.

However, I'm not sure how readable each of these solutions will be in the end on the final report.

@ramonski
Copy link
Contributor

This might solve the issue: Kozea/WeasyPrint#666

@ramonski ramonski removed the bug label Feb 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants