Created attachment 53909 [details] example of the bug Hi everyone, I've found a bug in LibreOffice (3.4.4) Writer concerning the border of a table. In my document, I have a lot of tables like this one: ++++++++++ +A1+ B1 + + +B2+C2+ ++++++++++ +A3+B3+C3+ The table head consists of the rows A and B. Cells A1 and A2 are merged, the same for B1 and C1. So. When I choose a bottom and a top border for rows A and B (width: 0,5pt), there is a little visible break between the bottom border of cell A1 and B2. One could avoid the problem by using a top border for row C instead of a bottom border for row B, but this workaround isn't useful if the table is longer than the page. In this case, the repeated table head wouldn't have a bottom border. Since I know that my explanation might be difficult to understand, I've created a example PDF and ODT file. You can download them from Google Docs: http://goo.gl/65BnB (PDF) http://goo.gl/IJYgP (ODT) The first table shows the break (you probably have to zoom in), the second the workaround. In my oppinion, there shouldn't be a visible difference between table 1 and 2, so I think that this is a bug. Julius
Created attachment 53910 [details] example of the bug (PDF)
reproduced on 3.5.0 rc 3 and 3.6.0 master on Fedora 64 bit but not reproduced in 3.3.4, therefore regression bottom border in first table misplaced, but displacement is very small, my be hard to find it on screen
[Reproducible] with "LibreOffice 3.4.1RC1 – WIN7 Home Premium (64bit) English UI [OOO340m1 (Build:101)]", I believe tht came with 3.4.0 If this one is a "Most Annoying Bug", I really would like to see an example for a "Normal" one :-/
regression between 3.3->3.4 => bibisected35older
@Rainer Bielefeld I finally understand your comment about the "most annoying bug". I just want to mention that it wasn't me who added the bug to this category.
I added this to MAB because of regression. Sorry for misunderstanding.
cannot reproduce on current 3.5, 3.6 or master; turns out it's fixed by the fix for bug 39415 *** This bug has been marked as a duplicate of bug 39415 ***