(This is the Impress equivalent of bug 32531) When moving in the same direction across text in an LTR table, and passing via a single RTL column, the cursor will only pass one position in the RTL column - to the left of all of the text - and proceed to move to the next LTR column. To reproduce: 1. Create a new impress presentation. 2. Be in an LTR slide. 3. Add a table with at least 3 columns (double-check they are LTR). 4. Choose a row and add some text to each column of that row (e.g. "hello"). 5. Make the second leftmost colum RTL, e.g. by selecting the whole column and pressing the RTL paragraph button on the toolbar. 6. Place the cursor at the leftmost point in the leftmost column, in your chosen row with the text. 7. Repeatedly move the cursor to the right using the right arrow key. 8. Note the sequence of cursor positions. Expected: The cursor traverses all points between characters in each of the columns as well as the left and right sides of the text in each column. Actual: The cursor reaches the left side position in the RTL column as expected, then continues to the left side position on the next LTR column to its right. The rest of the traversal is as expected.
Created attachment 182436 [details] Presentation for easily experiencing the bug This presentation has a table with one RTL column, and text in every column. Move the cursor from the leftmost character rightwards to experience the bug.
I reproduce. I don't know about the meta bug, because this can be reproduced in a non-RTL UI (not having to use SAL_RTL_ENABLED=1). Arch Linux 64-bit, X11 Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 9ee1b714c13db308c199172ffa0199405ca3d9c3 CPU threads: 8; OS: Linux 6.1; UI render: default; VCL: kf5 (cairo+xcb) Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Built on 14 February 2023
Seen in 3.5 as well, so probably inherited.
> I don't know about the meta bug, because this can be reproduced in a non-RTL UI Ok, switching to the more general meta-bug.
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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Bug still manifests with: Version: 25.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 2305fe302e12c4256e452589e2533772d4213e59 CPU threads: 4; OS: Linux 6.6; UI render: default; VCL: gtk3 Locale: en-IL (en_IL); UI: en-US Date: 2024-12-24