https://bugs.documentfoundation.org/show_bug.cgi?id=135620
John Kaufmann <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|WORKSFORME |--- Status|RESOLVED |REOPENED --- Comment #18 from John Kaufmann <[email protected]> --- Agreed: merges no longer break the exterior border (that is, transfer the interior lack of border to the exterior), but at a curious cost. I've been trying to figure out the connection, and finally decided that I will have to just describe it, and hope someone else sees the connection. Make a simple 3x3 table, with contents -- A1 B1 C1 A2 B2 C2 A3 B3 C3 -- and put border around the outside, but no borders between columns or rows. This is enough to test most merge situations, and all seem to behave properly and Undo properly. Now make the 3x4 table a 4x3 table by Insert|Column|After -- A1 B1 C1 D1 A2 B2 C2 D2 A3 B3 C3 D3 -- and the first strange thing happens: the outside border copies to the inside, between columns C and D. But it's not just Insert|Column|After. Insert|Column|Before gives this -- A1 B1 C1 A2 B2 C2 A3 B3 C3 or (depending on whether a cell or column is pre-selected) this -- A1 B1 C1 A2 B2 C2 A3 B3 C3 -- which also copies the outside border to the inside. As with columns, similar things happen with rows when you go to a 4x4 table, but I won't belabor the point further with examples. Moreover, properties of cell text contents are not maintained to the new row or column - again, I won't lengthen this further with examples. All of these behaviors can be worked around, but are clearly buggy if one expects tables in Draw to behave as in Writer or other LO components -- which begs the obvious question: in an integrated office suite, should not tables use the same code across components? The basic problem may be that a table is a "Shape" in Draw -- as opposed to, say, a functional table in a frame or box. So this bug may be considered superficially "FIXED" -- but on code that will raise new problems. On that basis, I'm changing Status from "RESOLVED-FIXED" to "REOPENED" until dev can consider this comment. Maybe that's the best we can do for now? -- You are receiving this mail because: You are the assignee for the bug.
