Download it now!
Bug 121112 - split line position not restored correctly (xlsx)
Summary: split line position not restored correctly (xlsx)
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.0.1.1 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:xlsx
Depends on:
Blocks: XLSX
  Show dependency treegraph
 
Reported: 2018-11-02 01:49 UTC by perlancar
Modified: 2019-10-03 03:02 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description perlancar 2018-11-02 01:49:37 UTC
Steps to reproduce:

1. Create a new spreadsheet

2. Drag the split line, e.g. the vertical split line to the right of column A and the horizontal split line to the bottom of row 1.

3. Save as XLSX

4. Close the spreadsheet

5. Reopen. The split lines position is now at ~column E, row 7.
Comment 1 raal 2018-11-09 19:11:08 UTC
No repro with Version: 6.2.0.0.alpha1+
Build ID: b0da1ca2d7a426ff13f39b21362fbcd5c0580c24
CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: gtk3; 
Please try with newer version, http://www.libreoffice.org/download/
Comment 2 QA Administrators 2019-09-02 09:30:53 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2019-10-03 03:02:18 UTC
Dear perlancar,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp