<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - freeze rows/columns functions incorrect or unexpected when frozen rows/columns don't fit in Window" href="https://bugs.documentfoundation.org/show_bug.cgi?id=112641#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - freeze rows/columns functions incorrect or unexpected when frozen rows/columns don't fit in Window" href="https://bugs.documentfoundation.org/show_bug.cgi?id=112641">bug 112641</a> from <a class="email" href="mailto:h.klene@gmx.de" title="Holger Klene <h.klene@gmx.de>"> Holger Klene</a> <pre>Another sidenote on the suggested ternary state: I think, it doesn't affect the saved file. The new "temporarily suspended" depends on the viewport, that may be completely different the next computer, LO is opening it. So from a persistence perspective cells are binary frozen or not. So the saved binary state expresses the users intention of how the table is supposed to work on an sufficiently big enough screen (this is to be save in the file). In contrast the ternary state is what Calc should make of it if squeezed into insufficient space (this is not to be saved directly, only derived from the saved state).</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>