https://bugs.documentfoundation.org/show_bug.cgi?id=124653
Adrian E <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #15 from Adrian E <[email protected]> --- I can confirm this is still a bug in the following LO version Version: 7.3.7.2 / LibreOffice Community Build ID: 30(Build:2) CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb) Locale: en-US (en_US.UTF-8); UI: en-US Ubuntu package version: 1:7.3.7-0ubuntu0.22.04.4 Calc: threaded This bug also appears to also act on a per-axis basis, so for example, if I have both frozen rows and frozen columns, and I shrink the height such that not all the frozen rows are visible, only the frozen rows will be reset, I will still be able to horizontally scroll and the frozen columns will stay as they were supposed to be. In my own experience, I have been annoyed by this issue for at least a couple years, especially since I use an LTS version of a popular Ubuntu-based desktop environment that seems to has a bug where plugging in external monitors causes all windows to resize themselves to be really small, thus causing this bug to be unintentionally reproduced quite frequently on my machine, requiring me to take several clicks and seconds to to disable (because its still enabled) frozen rows and columns and then re-enable them to reset the document's behavior. Despite only being a few clicks and a few seconds, the frequency with which this happens adds up quickly. As the wise XKCD authors suggest in comic 1205, it seems as though each person in a similar situation to mine can afford to spend a low-single-digits number of hours fixing this issue before it becomes more effort than it would save. I would also be interested in understanding the reasoning behind why fixing this issue not possible for safety reasons. One potential solution I believe might work: If the behavior for handling frozen rows and columns was configurable in the settings, a note explaining the safety issue could potentially be added either in settings or as a popup upon changing the setting. This would resolve the concerns with being intrusive to users with repetitive notifications as they would only see a notification if they changed that setting from its safety-first default. This would also not require substantially more computation every time a window is resized as it would act to prevent the "disable frozen rows/cols" behavior in the first place, rather than trying to selectively re-introduce it back in. -- You are receiving this mail because: You are the assignee for the bug.
