Bug 155694 - Changing the direction of an RTL table causes the black borders to become garbled
Summary: Changing the direction of an RTL table causes the black borders to become gar...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
7.5.3.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: RTL
  Show dependency tree / graph
 
Reported: 2023-06-05 17:19 UTC by Hossein
Modified: 2024-08-19 11:36 UTC (History)
0 users

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Hossein 2023-06-05 17:19:24 UTC 
Description:
Changing the direction of an RTL table causes the black borders to become garbled.

Steps to Reproduce:
1. Open ODT attachment 187737 [details] in LibreOffice.
2. Select the whole table.
3. Make it LTR by setting "Table Properties > Table > Text Direction" to "Left-to-Right (LTR)".
4. For the reference, do the same in MS Word.

Actual Results:
The black border line becomes garbled.

Expected Results:
The black border should remain the same. In MS word, the black borders remain unchanged.

Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 7.5.3.2 (X86_64) / LibreOffice Community
Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3
CPU threads: 20; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win
Locale: en-US (en_DE); UI: en-GB
Calc: CL threaded
Comment 1 ysui2022 2023-07-05 21:01:06 UTC 
I reproduced the bug successfully. The table did become garbled.

Version: 7.5.4.2 (X86_64) / LibreOffice Community
Build ID: 36ccfdc35048b057fd9854c757a8b67ec53977b6
CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win
Locale: zh-CN (zh_CN); UI: zh-CN
Calc: CL threaded
Comment 2 Eyal Rozenberg 2024-08-19 11:36:56 UTC 
Can this be reproduced from scratch? Or does it rely on the original document being an MSO DOC file, which introduces some weird structural elements?