https://bugs.documentfoundation.org/show_bug.cgi?id=123432
V Stuart Foote <vstuart.foote@utsa.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |vstuart.foote@utsa.edu
--- Comment #5 from V Stuart Foote <vstuart.foote@utsa.edu> ---
I really see no advantage in switching the Zoom view (and by default the normal
page presentation in the UI) to "multiple-page" (i.e. a multi-column canvas
layout). Doing so would remove established behavior of working with a single
page document canvas just to shift document display to multiple-columns and
chase a MSO behavir. Not appropriate as any substantive editing of the
document would require a zoom back into ranges correctly handled as single-page
view.
Also, changing from "automatic", i.e. "Multiple-page view" mode, to single
column, i.e. "Single-page view" mode has other issues like bug 40105 and bug
90468 for the active cursor placement and zoom focus. Or those of bug 98446 for
the Hide whitespace behavior toggle back to single-page mode. Or as in bug
95575 for setting the zoom factor when entering multi-page mode.
To my mind we are better served by keeping our legacy behavior of single
column/single-page view mode as default as it is most stable and best behaved
for UX.
--
You are receiving this mail because:
You are on the CC list for the bug.
Context
- [Libreoffice-ux-advise] [Bug 123432] Zoom View Layout Automatic as default · bugzilla-daemon
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.