Created attachment 149910 [details]
Source file with fields in right position
The attached spreadsheet form display fields correctly positioned and *all* fields (text box, radio buttons, list box) are anchored in cell and their size were set "adjust size to cell size" (or the like in English), using context menu on selected fields.
Symptom: On exporting to PDF form, the fields are shifted to wrong position, often overlapped and makes PDF form unusable.
* The effect seems random. Sometimes it works, sometimes it produces a messy PDF.
* it seems to depend on saving and reopening the file
* on adding or removing lines/columns/cells,
* perhaps on cell position recalculation in page, with effect on anchoring.
* On cell rendering, the field anchoring changes, seems to shift to a neighbor cell
* field size does not follow cell size.
* suspicion on rounding number for cell position and field position calculation.
* suspicion on memory leak or uninitialized variable.
Affects LibreOffice 6.1.5 and later, not tested with earlier versions.
Tested on Linux (6.2.1 and okular) and Windows (LO 6.1.5, with display in Acrobat Reader DC)
Created attachment 149911 [details]
Produced PDF file with fields in worng position
Some further information:
* On exporting each sheet in one PDF document (1 sheet per page), the fields are not shifted.
* After opening the form, it seems that the page rendering is introducing small offsets in cell position and often the anchor jumps to a neighbor cell.
Does setting "Use printer metrics for text formatting" (Tools -> Options -> LibreOffice Calc -> General: Input settings checkboxes) and tweaking the fielded sheet help to hold positions on export to PDF?
Working the test document, I see cells shift within Calc when setting unsetting the use printer metric value. But the PDF export is consistent with/without.
Don't know if that is full extent of the layout changes you see, but may be contributing. And of course we can't leave the printer metrics enabled all the time as it kills sheet performance.
Another hint that help to overcome the issue:
1) Open the spreadsheet form,
2) do all editions, set all fields positions.
3) *save file*
4) *close file*
5) Open file
6) export to PDF. *Do not edit file before exporting to PDF*
I could not reproduce. Made a test by inserting a row, exporting to PDF.
Arch Linux 64-bit
Build ID: 4bd1b38633d6cb288eb559afc0ac6b961538ae60
CPU threads: 8; OS: Linux 5.2; UI render: default; VCL: gtk3;
Locale: fi-FI (fi_FI.UTF-8); UI-Language: en-US
Built on 24 July 2019
Hello Olivier Hallot,
Is this issue still reproducible with the latest version of LibreOffice from
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the bug is still present in the latest version.
Dear Olivier Hallot,
This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INSUFFICIENTDATA
due to lack of needed information.
For more information about our NEEDINFO policy please read the
wiki located here:
If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.
Thank you for helping us make LibreOffice even better for everyone!
Dear Olivier Hallot,
Please read this message in its entirety before proceeding.
Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):
a) Provide details of your system including your operating
system and the latest version of LibreOffice that you have
confirmed the bug to be present
b) Provide easy to reproduce steps – the simpler the better
c) Provide any test case(s) which will help us confirm the problem
d) Provide screenshots of the problem if you think it might help
e) Read all comments and provide any requested information
Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:
a) respond via email
b) update the version field in the bug or any of the other details
on the top section of our bug tracker