Description: after grouping columns A-D or Row 1 respectively and colapsing the group this rows/columns are no longer displayed, but there is no button to open the group. The rows/columns are not "hidden" and can not be "shown" either Actual Results: Expected Results: Reproducible: Didn't try User Profile Reset: No Additional Info: 7.2 alpha does not show the rows/columns either. Microsoft excel does thought.
saving as xslx and reopening in calc retored the missing columns, but not the single grouped row 1
Created attachment 172750 [details] spreadsheet showing the problem further experimentation shows the problem is related to "freeze row/columns" too. Unfreezing will at least show the missing columns A-D again. Column 1 still missing though.
dang, in the curse of preparing testcase.ods the column problem vanished. My original file no longer has the column problem either. But row 1 is still missing in both files.
When reporting, first make all clear in a single post if possible You need to write exact steps to reproduce problem, so Needinfo. In general, when you figure out the issue, search if already reported.
The appended calc file shows the missing row 1 problem Just open it and see if you can access row 1 I'm using 7.2 alpha now, but the problem still persists I'm sorry, but I'm not able to provide a reproduction recipe cause I'm not sure when and how it happend. All I can say is that it seems to have to do with grouping leading row (1...) or columns (A...) and freezing rows and columns. The missing columns A-D at least reapeared when I lifted the freeze.
[Automated Action] NeedInfo-To-Unconfirmed
Thanks for reply, but I set Needinfo again. Because like this without steps it may stay open for a long time, unlike Needinfo which will close in nobody is able to explain in 6 months. So please do not reply if you don't have steps, just wait.
I can provide the steps and a sample for Version: 7.0.6.2 (x64) Build ID: 144abb84a525d8e30c9dbbefa69cbbf2d8d4ae3b CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: sv-SE (en_GB); UI: en-GB Calc: threaded Create a new sheet Enter any data in A1 - It's a good idea to use anything in the sort lists so cells can be auto filled by expansion Select A1 and expand horizontally to column I Select A1:I1 and expand vertically to row 17 You will observe a matrix A1:I17 Select columns A - C and from >Data>Group & Outline>Group (F12) Select Rows 1 - 8 and from >Data>Group & Outline>Group (F12) Conceal the Column group Conceal the Row group At this point it may be necessary to save and reload the sheet as it is affected by file saves. Activate the Column group it MAY refresh all Columns -- inconsistent Activate the Row group, Row 1 is now missing It may be "recovered" by selecting the entire sheet at the conjunction of Columns and Rows then right-click the Row Border and select "Show Rows" Sometimes, the group handle on the recovered rows has been reassigned from rows 1 - 8 to now only include rows 2 - 8 Does that help?
Created attachment 173979 [details] Sample Calc
I can confirm that with Lorenz's sheet the selection of the entire sheet will permit the right clicking of the row boundary and "Show Rows". As per my description, the group handle now only encompasses row 2
I can confirm that with my sheet, the same symptoms and remedies I defined are exhibited in; Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 67f2a99229101757af4f40118f4d3c83ba38648b CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: en-GB (en_GB); UI: en-GB Calc: threaded It's conceivable Lorenz's experience with Freeze Rows and Columns exacerbated whatever he was testing but the symptoms on his sheet were remedied by my actions even with the active Freeze. Releasing the Freeze after the remedial actions simply refreshed the anticipated display.
Sounds like a duplicate of bug 116663, please see 2 problems in Comment 4. If you think it's not, please explain. If that bug is resolved, then saving to XLS/X should be tested. *** This bug has been marked as a duplicate of bug 116663 ***