Created attachment 143542 [details] The two-column table in .odt (with some stuff before and after the table) 1. Create a 2-column table with one row. 2. Set outer border only. 3. Fill something in. 4. Save as .odt 5. Save as .docx. 6. Reopen the two files. The .odt reopens correctly, while the .docx reopens with an extra (unneeded) vertical line -- column divider.
My results were a bit different. The docx. does have the vertical line. However, the .odt file has a vertical line that is light gray, sort of a disabled look. I have attached a screenshot of this when tested in 6.2; however, it occurred in both of the following builds.
Created attachment 143544 [details] odt file with vertical border seen Shows the "disabled" vertical line seen in odt calc file after following reported steps.
Created attachment 143545 [details] No vertical line No vertical line on my end (Mac 10.9.5).
Confirm the "extra (unneeded) vertical line -- column divider" Version: 6.2.0.0.alpha0+ Build ID: 46855d3a98b515f334c447707c533025cfe98a48 CPU threads: 8; OS: Linux 4.14; UI render: default; VCL: kde4; Locale: nl-BE (en_US.UTF-8); Calc: group threaded
add to comment4 saving the document as .docx will show the problem
Saving as .doc (as opposed to .docx) does not result in creation of the unneeded vertical line.
This seems to be a regression. I tried to bisect it with bibisect-43max but the result is no accurate... Maybe someone can bisect it with lo-linux-dbgutil-daily-till43 ?
bisected to the same commit as bug 82177. Hack fixable with else if ( !rStyleProps || !rStyleProps->LineWidth ) // no line, and no line set by the style either: // there is no need to write the property + {} - return; *** This bug has been marked as a duplicate of bug 82177 ***