ONLYOFFICE / DocumentServer

ONLYOFFICE Docs is a free collaborative online office suite comprising viewers and editors for texts, spreadsheets and presentations, forms and PDF, fully compatible with Office Open XML formats: .docx, .xlsx, .pptx and enabling collaborative editing in real time.
https://www.onlyoffice.com
GNU Affero General Public License v3.0
4.83k stars 1.09k forks source link

Some lines of the book are hidden after re-saving the XLSX file #1565

Open nobt854 opened 2 years ago

nobt854 commented 2 years ago

Do you want to request a feature or report a bug? bug What is the current behavior? Hidden row problem occurs after excel file is saved If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.

  1. Use ONLYOFFICE to open the file: Source file
  2. Download as xlsx format through the file menu function : After-open-and-saved-by-onlyoffice
  3. Use other excel tools locally to open the downloaded new excel file, such as Microsoft Excel
  4. There are problems such as hidden lines from 136 to 171 lines, 173 lines to 206 lines hidden, 208 lines to 272 lines hidden, 274 lines to 315 lines hidden... etc.

What is the expected behavior? Do not hide these hidden rows Did this work in previous versions of DocumentServer? don't know DocumentServer version: 6.4.2 Operating System: windows Browser version: chrome 96.0.4664.45

VladimirProkofiev52 commented 2 years ago

Hello. @nobt854, I can confirm - this is bug, issue 54726 in our private issue tracker. Thank you for report.

nobt854 commented 2 years ago

@VladimirProkofiev52 Can this be confirmed as a problem caused by the front-end rendering process based on Editor.bin, or a problem caused by the back-end excel transfer to Editor.bin?

ShockwaveNN commented 2 years ago

@nobt854 Sorry, I don't think QA department has enough knowledge to pinpoint this issue to a specific component, but just by my experience I think it's may be related to backed convert to Editior.bin

nobt854 commented 2 years ago

@ShockwaveNN Many thanks