Description: Position of the image affected footnote rendering on screen & footnote distance at PDF export Steps to Reproduce: 1. Open the attached file 2. Drag the image around as in screencast 3. See wrong rendering on the second page. Which only looks as some footnote painting error (which doesn't correct after zoom in/out 4. Export to PDF -> Notice that does make a difference 5. Save & reload -> Different layout of doc in question Happens with 'to character' and 'to character' -> I reported this before somewhere, but ended up being a duplicate.. (except the PDF export part) Actual Results: Footnote distance isn't broken because of image position Expected Results: This situation shouldn't occur Reproducible: Always User Profile Reset: No Additional Info: Version: 7.1.0.0.alpha0+ (x64) Build ID: 4c14c88cc681abab787a461a1bea502a777f37e6 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL
Created attachment 162567 [details] Example file
Created attachment 162568 [details] Exported PDF belong to screencast
Created attachment 162569 [details] Screencast
Created attachment 162572 [details] Example file (easy bibisect) Clipped footnote on file open export fine
(In reply to Telesto from comment #4) > Created attachment 162572 [details] > Example file (easy bibisect) > > Clipped footnote on file open export fine Inherited :-(
*** Bug 132249 has been marked as a duplicate of this bug. ***
(In reply to Telesto from comment #0) > -> I reported this before somewhere, but ended up being a duplicate.. > (except the PDF export part) You are not talking about bug 132249, I guess. But can you add informations about that bug, you've reported before? Thank you.
Repro NixOS Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: 67e47070a7580a17804adce812cc2f98bfe7b51f CPU threads: 16; OS: Linux 5.13; UI render: default; VCL: x11 Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded
Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug