Details
-
Task
-
Resolution: Fixed
-
Major
-
16.10.14
-
None
-
Integration
-
Unknown
-
Description
We are currently using this Docker image https://hub.docker.com/r/zenika/alpine-chrome to run headless Chrome on the server-side for PDF export. This image has a couple of problems:
- it provides an old version of Chrome, 124, versus the current 144 version
- using a 2-years old Chrome version poses a security threat
- recent versions of Chrome have added support for:
- generating PDF outline (bookmarks)
XWIKI-23380 - generating tagged PDFs that are accessible (properly read by a screen reader) XWIKI-19560
- generating PDF outline (bookmarks)
- I haven't checked, but recent versions of Chrome should be faster as well
- even though the provided Chrome version is old, the image seems to be updated often, by reusing the same tag. Which means that, even if the image version is fixed on our side, the behavior could be different depending on which iteration of the same version was cached locally... See
XWIKI-23703for the surprise I recently had.
Based on this I think we should look for an alternative. This one https://hub.docker.com/r/femtopixel/google-chrome-headless seems to be a good option.
Attachments
Issue Links
- blocks
-
XWIKI-19560 The browser-based PDF export doesn't pass accessibility checks
-
- Open
-
-
XWIKI-12192 Tables resized in wysiwyg overflow in the PDF export
-
- Closed
-
-
XWIKI-22162 The last lines of text from a print page are not always visible when they are inside a table cell that is split between print pages
-
- Closed
-
-
XWIKI-23380 Include an outline (bookmarks) in the generated PDF
-
- Closed
-
-
XWIKI-23695 Limit how low the table cell width can go while exporting to PDF
-
- Closed
-
- relates to
-
XWIKI-19144 Image alternative text is lost during PDF export
-
- Open
-