Created attachment 103078 [details]
Screenshot highlighting the issue with the table
Steps to reproduce the bug:
1. Open attachment 81684 [details] in Writer 4.3
2. Open attachment 81684 [details] in Writer 4.4
3. Compare the documents.
Note the right border is incorrectly rendered in recent 4.4 builds.
In windows, Version: 126.96.36.199.alpha0+
Build ID: f38bf4c6c29d685ec4f1015be09f64c7ae2eb172
TinderBox: Win-x86@39, Branch:master, Time: 2014-07-04_02:13:48
Build ID: eddd7646d672ea9b0561dacb09da224d098e531e
TinderBox: Win-x86@39, Branch:master, Time: 2014-07-18_06:42:50
very recent 4.4.x regression
table was rendered correctly in 188.8.131.52.alpha0+
Build ID: abc28ffc04067eb24840fbf564c311aaee10f84d
TinderBox: Win-x86@42, Branch:master, Time: 2014-07-15_07:20:05
table has missing right border in 184.108.40.206.alpha0+
Build ID: b9dca968c6fd0ab5ca140c65b0e54d153cd34986
TinderBox: Win-x86@42, Branch:master, Time: 2014-07-18_22:51:20
Created attachment 103081 [details]
minimal test case
easier to debug
In MS Word 2007, when you force the table to the left column by inserting a manual page break above it, the border disappears just like Writer.
The real issue here is why is 4.4 doing a worse job of laying out the page? Why does the table end up in the wrong page and column? Is there something between "related project plan." and "Revenue Forecasting" that is causing 4.4 to move the text to a new page?
Since this is a layout issue not a table issue, should I open a new report or should I just change the title?
Word 2013 also cuts off the right side of the border when the table is pushed to the next page.
Between "marketing claims." and "License Agreements" there is a column break that the prior versions of Writer were not respecting.( 2 bugs were canceling each other out) The issue here is the 3D bar chart is positioned incorrectly, pushing all the text down. I'll create a new bug report for that. In the meantime, I'll close this as "Not a Bug"
Migrating Whiteboard tags to Keywords: (bibisectRequest)
The 3D bar chart is positioned incorrectly because of Bug 82824.