Description: In DOCX format Border padding is not saved for image when in a table. I.E. if you put a value in for padding this is not saved. Steps to Reproduce: 1. Create a table 2. Place an image in a cell (png) 3. Change the borders padding to 0.10 4. Save as ODT works 5. Save as 365 docx format 6. Reopen borders padding is 0 Actual Results: Border padding is saved Expected Results: Border padding is reset to 0 Reproducible: Always User Profile Reset: No OpenGL enabled: Yes Additional Info: Saving as ODT format keep the values. I am looking into this now but this is my first foray into LibreOffice so waiting for it to build. Would handy to speak with someone on next steps. Happy to help
Built this source git log --pretty=format:'%h' -n 1 209d07ff2de2 And this is still present.
Created attachment 171210 [details] Example file created by instructions
Created attachment 171212 [details] The example file saved as docx With yesterdays nightly: Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 77419c6f3aba1fd5b1660795923c22a39bdb1bad CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win Locale: en-US (hu_HU); UI: en-US Calc: CL
Created attachment 171214 [details] The example file and its docx version side by side in Writer The images padding is lost regardless of it being inside a table or not.
On the other hand: I'm unable to find an equivalent setting on Words UI. There is only "Distance from text" which is equivalent to Properties - Wrap - Spacing in Writer; the distance between the border line and the surrounding text. But I see no option to set the padding between the image and the border line.
So being my trek to track this down padding is stored in the content.xml. Will now look at where this is in the DOCX version. All a bit new so maybe a bit slow.
Dear Bill Wiseman, 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
This is a format limitation of DOCX and DOC apparently. I know that for paragraphs, the border distance is limited to 31pt, so our export code tries to compensate by adding it to the margins. In this case, it would have to take the value and move it to the wrap margins. However, that is a lot of computer guesswork and emulation, so probably better to leave it for the human to work out. Long story short - LO can do things that MSO can't.