Bug 81080 - FILESAVE: Comments visibility does not save properly in xlsx format
Summary: FILESAVE: Comments visibility does not save properly in xlsx format
Status: RESOLVED DUPLICATE of bug 76406
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
4.2.4.2 release
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2014-07-09 06:47 UTC by jan
Modified: 2014-07-12 17:45 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
Screenshot of one of my working sheets after opening. (379.95 KB, image/png)
2014-07-09 06:47 UTC, jan 		Details
test .ods - save it to .xlsx to reproduce bug (11.18 KB, application/vnd.oasis.opendocument.spreadsheet)
2014-07-11 04:48 UTC, tommy27 		Details
View All 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 jan 2014-07-09 06:47:41 UTC 
Created attachment 102458 [details]
Screenshot of one of my working sheets after opening.

Problem description: When saving spreadsheet to xlsx format, after reopening all comments are shown, blocking the view of actual cells behind them.

Steps to reproduce:
1. Modify or create spreadsheet with comment and set the comment to hide, so it shows on mouse-hover.
2. Save the sheet in xlsx and close it.
3. Reopen it.

Current behavior: Comments are all shown.

Expected behavior: Comments should be hidden and be shown only when mouse hovers over them.

              
Operating System: Ubuntu
Version: 4.2.4.2 release
Comment 1 tommy27 2014-07-11 04:48:51 UTC 
Created attachment 102591 [details]
test .ods - save it to .xlsx to reproduce bug

I confirm bug with LibO 4.2.5.2 under Win7x64 this affects only .xlsx saving while .xls works fine.

interestingly if you open the resulting .xlsx in Excel viewer the comment is hidden so it's basically a FILEOPEN issue of LibO.
Comment 2 tommy27 2014-07-11 04:52:00 UTC 
issue was already reported.

*** This bug has been marked as a duplicate of bug 76406 ***
Comment 3 jan 2014-07-12 17:45:22 UTC 
Thanks for the heads-up tommy.