I am writing a large .docx document in LibreOffice Writer with several tables. I want the tables to only have horizontal lines above and below the first row and under the last row and no vertical lines.
However every time I save, close, and open the document the tables show up with horizontal lines everywhere and I have to remove them again.
Steps to Reproduce:
1.Create a large .docx file with many tables.
2.Format the lines on the tables, removing all except lines above and under 1st row, and under last row.
3.Save, close, and reopen the document.
All horizontal lines now show up. Even if deleted again, they appear the next time the document is opened.
The tables should remain as formatted, with horizontal lines only above and under the 1st row, and under the last row.
User Profile Reset: Yes
OpenGL enabled: Yes
The file was edited at some point by a collaborator in Word and contains Zotero references.
Version: 188.8.131.52 (x64)
Build ID: 54c8cbb85f300ac59db32fe8a675ff7683cd5a16
CPU threads: 8; OS: Windows 10.0; UI render: default;
Locale: en-US (en_US); Calc: CL
Reproducible with Version: 184.108.40.206 (x64)
Build ID: b3972dcf1284967612d5ee04fea9d15bcf0cc106
CPU threads: 12; OS: Windows 10.0; UI render: GL;
Locale: ru-RU (ru_RU); Calc: CL
Steps to reproduce:
1. Create a new text document in Writer.
2. Add a table with 3 or more rows.
3. Select the table (TableSelect→Table), and set to no borders using Borders on Table toolbar.
4. Select top row, and set top and bottom lines using the same tool.
5. Select bottom row, and set bottom line using the same tool.
6. Save as DOCX and reopen.
Expected: table lines stay as manually set.
Actual: table has all horizontal lines set.
Regression introduced in range https://cgit.freedesktop.org/libreoffice/core/log/?qt=range&q=49a96a4d38ed144f6d05a0d2d8a83c2cee52b304..214751e3cc5b154d90963f4abf0a9317733b001b
https://cgit.freedesktop.org/libreoffice/core/commit/?id=ae61569eea0719a882010cfbb260a1a0d690d974 looks like a good candidate...
Marking as duplicate since it has the same regression commit, and since the same hack that fixed another duplicate Bug 118753 also fixed this one.
*** This bug has been marked as a duplicate of bug 82177 ***