Created attachment 144787 [details]
The tables in the attached DOC went between Word and Writer back and forth, that's why they are both in frames. Actually, the DOC has been saved from the DOCX original attachment 144783 [details] of bug 119800.
In Writer no tables are shown. In Word it looks the same as attachment 144785 [details], and the exported PDF looks the exact same as attachment 144786 [details].
If the supposedly invisble content is removed from the document via Inspect Document in Word, both tables appear in Writer (positioning is slightly off, though, but also in Word, mosty likely spacing from the invisible empty paragraph).
Observed using LO 6.2 daily build (2018-09-07_23:40:38, 9a9b81c7212fa6a6762246593acf3f1950677a22) & 220.127.116.11 / Windows 7.
In 18.104.22.168 only the table on the left isn't shown.
In 3.3.0 both tables are shown.
The regression between 4.0 and 4.4 could be bibisected.
Created attachment 144788 [details]
Sample DOC with "hidden text" removed
Bibisected the second change to the following commit with repo bibisect-44max.
The first change occurs before 3.4 => notBibisectable
author Caolán McNamara <firstname.lastname@example.org> 2014-09-23 20:35:50 +0100
committer Caolán McNamara <email@example.com> 2014-09-24 10:04:48 +0100
WW8PLCFMan::AdjustEnds deeply flawed concept wrt change tracking
confirm it in
Version: 22.214.171.124 (x64)
Build ID: 5d19a1bfa650b796764388cd8b33a5af1f5baa1b
CPU threads: 4; OS: Windows 10.0; UI render: GL;
Locale: ru-RU (ru_RU); Calc: CL
(In reply to Aron Budea from comment #2)
> Bibisected the second change to the following commit with repo
> The first change occurs before 3.4 => notBibisectable
The correct keyword for that is preBibisect.
Dear Aron Budea,
To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.
There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.
If you have time, please do the following:
Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/
If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.
Please DO NOT
Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not
appropriate in this case)
If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/
2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword
Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!
Still repro in
Version: 126.96.36.199.alpha0+ (x64) / LibreOffice Community
Build ID: bff60eadeac348024849d710690435ee9580831b
CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win
Locale: ru-RU (ru_RU); UI: en-US