Created attachment 138969 [details] Document manifesting the bug Perform the following: 1. Set default style direction to RTL 2. Created a 1x2 table (1 row, 2 columns 3. Enter text in each cell: A, B 4. Set the first cell (should be rightmost cell in RTL order) to have vertical flow (e.g. via the menus: Table | Properties | Text Flow | Text orientation) 5. Save & close the file 6. Open the file you just saved Result: The entire line's rendering gets shifted to the left. You can see this by comparing the "before closing" and "after reopening" screenshot. This _seems_ to be a problem with the way LO loads saved data, as the problem does not occur with this layout before the file is closed and reopened. It is probably not a problem with the saving code, since we're also seeing this issue (and another one) in the blocked bug 114883 - where the file was saved in Microsoft Word (and opens correctly with Word). Notes: * The bug manifests per-line, so if you make the table 2x2, and only change the layout to vertical on the second line, you'll only get a shift on the second line. * If the line has just one cell (which gets oriented vertically), the bug doesn't manifest. * You can't see the attached ODT _without_ the bug - you have to create a new document for that. Thanks go to Mike Kaganski for "extract"ing this simplified issue out.
Created attachment 138970 [details] "Before" screenshot (after step 4) Screenshot of how the table _should_ be laid out, and _is_ laid out before we close the document file.
Created attachment 138971 [details] "After" screenshot (after step 6) Screenshot with the bug manifesting - after saving, closing and opening the document which exhibited the "before" shot.
Repro from scratch. Arch Linux 64-bit Version: 6.1.0.0.alpha0+ Build ID: 73c757ff71b6bf14206adf13a65213c79928a592 CPU threads: 8; OS: Linux 4.14; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group threaded Built on January 30th 2018 Arch Linux 64-bit LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4
*** Bug 92679 has been marked as a duplicate of this bug. ***
Created attachment 139450 [details] "Before" screenshot (after step 4) Previous version of screenshot used a 2x2 table (while the reproduction instructions only need a 1x2 table).
Created attachment 139451 [details] "After" screenshot (after step 6) Previous version of screenshot used a 2x2 table (while the reproduction instructions only need a 1x2 table).
Bug still manifests with: Version: 6.1.1.2 Build ID: 5d19a1bfa650b796764388cd8b33a5af1f5baa1b CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk2; Locale: en-GB (en_GB.UTF-8); Calc: group threaded
Dear Eyal Rozenberg, 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Bug still manifests as described with: Version: 6.3.1.2 Build ID: 1:6.3.1-1 CPU threads: 4; OS: Linux 5.2; UI render: default; VCL: gtk3; Locale: he-IL (en_IL); UI-Language: en-US Calc: threaded
Dear Eyal Rozenberg, 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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Bug still manifests with: Version: 7.1.3.2 (x64) / LibreOffice Community Build ID: 47f78053abe362b9384784d31a6e56f8511eb1c1 CPU threads: 12; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: en-US (en_IL); UI: en-US Calc: CL Additional notes on the reproduction instructions: * It doesn't matter if the paragraph alignment is Left, Right or Justified. * When you set the vertical alignment, you don't have to first make sure and select exactly the single cell; it's enough if you just have your cursor in that cell, for it to be the only one effected.
Bug still manifests with: Version: 7.2.0.1 / LibreOffice Community Build ID: 32efc3b7f3a71cfa6a7fa3f6c208333df48656cc CPU threads: 4; OS: Linux 5.10; UI render: default; VCL: gtk3 Locale: en-US (en_IL); UI: en-US
Reproduced from scratch in: Version: 24.2.0.0.beta1 (X86_64) / LibreOffice Community Build ID: 5f390384195b7264c6e52add9e90a39790285249 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded