https://bugs.documentfoundation.org/show_bug.cgi?id=163571
--- Comment #3 from Manu <[email protected]> --- (In reply to Nicole A. from comment #1) > Hello [user's name], > > Thank you for reporting the bug. > Unfortunately without clear steps to reproduce it, we cannot track down the > origin of the problem. > Please provide a clearer set of step-by-step instructions on how to > reproduce the problem. > I have set the bug's status to 'NEEDINFO'. Please change it back to > 'UNCONFIRMED' once the steps are provided Hello Nicole, thank you for your interest. I have reported the bug 161898 The first comment (Manu 2024-07-04 21:58:30 UTC) tries to explain how to create the anomaly and what is the perimeter/context necessary. I have again tested today, and I confirm the anomaly when using the procedure described in the bug_font_lineheight.ods Version: 24.8.2.1 (X86_64) / LibreOffice Community Build ID: 0f794b6e29741098670a3b95d60478a65d05ef13 CPU threads: 8; OS: Windows 10 X86_64 (10.0 build 19045); UI render: Skia/Raster; VCL: win Locale: fr-FR (fr_FR); UI: fr-FR Calc: threaded I would like to complete the comment made by Heiko because there are 2 side effects with live preview: - when we expand the font name drop down list, and hover over names (or cursor up/down), the live preview updates the selected cells (and consequently all the screen), and if the sheet is "complicated", then we can feel a delay when we change from one line to another line of font, and if I want to select the 20th font in the list (or farther), all these delays accumulate (using the keyboard). - after the exit of the font list (with click, enter or escape), the second side effect is visible (if the conditions are respected): the status bar blinks each time we move to another cell. This blinking is quick, but slow when the sheet is too complicated, I have seen one second delay for a 3mb file and the only formula is an equal to a cell with multiline text and each cell has a different font. Fortunately, I know how to disactivate this anomaly. But the normal user who discovers this anomaly for the first time, you imagine the hell: a big file with important and complicated data, each move is incredibly slow without explanation, mandatory to close and reopen the file, very bad experience. About the 100ms limit, it could be a good idea. Maybe we could propose different exits: 1- stop the font update mechanism (no user intervention, nor message box) 2- message box: dear user, the live preview is maybe too long for you, we can disable it for you. Select your answer: a (disable live preview for the current session), b (permanently, if you don't need it), c (you are ok to wait, we disable this warning for the current session), d (we stop the update after 100ms and disable this warning for the current session). I wonder if we could have a third exit case: the message box could explain how to disactivate the bug manually (focus on one cell only, click inside the text of the font list, type enter), or if the program can try to emulate these actions for the user. I hope it helps. Have a nice day all! -- You are receiving this mail because: You are the assignee for the bug.
