https://bugs.documentfoundation.org/show_bug.cgi?id=154103

            Bug ID: 154103
           Summary: Movement around a link is "LTRified" even in RTL
                    contexts
           Product: LibreOffice
           Version: 7.6.0.0 alpha0+ Master
          Hardware: All
                OS: Linux (All)
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: Impress
          Assignee: libreoffice-bugs@lists.freedesktop.org
          Reporter: eyalr...@gmx.com

Consider the attached single-slide presentation, with RTL text. If you:

0. Have two keyboard input languages enabled, an LTRish Western layout and an
RTLish layout
1. Place the cursor at the end of the second bullet point, which says שורה
שניה. Remember the end is at the left edge, since this is RTL content.
2. Make sure your cursor is pointing due left (corresponding to an RTL keyboard
layout) and hasn't been switched.
3. Press the left arrow key.
4. Paste the character א (copy it from here if needed).
5. Press the left arrow key.

Expected result:

Moving left - past the end of the paragraph - should bring us to the first
cursor position in the next RTL paragraph, which is before the hyperlink, i.e.
to the right of the hyperlink and facing left. Pasting the א places that letter
to the right of the hyperlink, with the cursor to its left and facing left.
Pressing Left should move the cursor past the hyperlink, to its left edge (and
before the space), continuing to face due left.

Actual results:

The cursor is placed to the _left_ of the hyperlink, facing _right_. Pasting
the א places the letter to the right of the hyperlink - and brings the cursor
to the right of the hyperlink as well, now facing left. Pressing left doesn't
move your cursor, but changes its orientation to now face right.

We don't see any of these weird cursor placements and re-orientations if we
just move between two lines of RTL text, due left from the leftmost of the
first of them.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to