Bug 123608 - FILEOPEN | XLSX, Arrows change direction when opened in Calc.
Summary: FILEOPEN | XLSX, Arrows change direction when opened in Calc.
Status: RESOLVED DUPLICATE of bug 83593
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
4.1.0.4 release
Hardware: All All
: medium normal
Assignee: Balázs Regényi
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: OOXML-Shapes
  Show dependency treegraph
 
Reported: 2019-02-21 08:41 UTC by NISZ LibreOffice Team
Modified: 2020-05-29 15:20 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
The original document. (18.07 KB, application/vnd.openxmlformats-officedocument.spreadsheetml.sheet)
2019-02-21 08:41 UTC, NISZ LibreOffice Team
Details
Screenshot of the original document side by side in Excel and Calc. (348.86 KB, image/png)
2019-02-21 08:42 UTC, NISZ LibreOffice Team
Details

Note You need to log in before you can comment on or make changes to this bug.
Description NISZ LibreOffice Team 2019-02-21 08:41:02 UTC
Description:
When the attached document is opened in LO the arrows change their direction.

Steps to Reproduce:
    1. Open the attached xlsx in LO and MSO.
    2. Notice the changes in LO.

Actual Results:
The arrows point in the opposite direction.

Expected Results:
They should keep their original direction.


Reproducible: Always


User Profile Reset: No



Additional Info:
Comment 1 NISZ LibreOffice Team 2019-02-21 08:41:44 UTC
Created attachment 149445 [details]
The original document.
Comment 2 NISZ LibreOffice Team 2019-02-21 08:42:05 UTC
Created attachment 149446 [details]
Screenshot of the original document side by side in Excel and Calc.
Comment 3 raal 2019-02-21 20:30:35 UTC
I can confirm with Version: 4.1.0.0.alpha1+
Build ID: 863d38fbfa4fb4861e476828c46410602100919 and 
Version: 6.3.0.0.alpha0+
Build ID: 465939feb0e9c382e5581b53b72008979ece4807
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3;
Comment 4 Szabolcs Toth 2020-05-29 15:20:16 UTC

*** This bug has been marked as a duplicate of bug 83593 ***