when you have in writer an document with more than one page and a large screen the zoom show always single page layout (widht). there is also in .uno:zoom the option automatic where you get more pages per column depending on the zoom. As this is the default on MSO I suggest to change the default in LibO to have also View Layout Automatic as default.
What is Automatic and how you set it? Do you mean "Multiple-page view"?
Created attachment 149256 [details]
writer -> Menubar -> View -> Zoom -> Zoom
right column set to Automatic instead of Single page
(In reply to andreas_k from comment #0)
> As this is the default on MSO I suggest to change the default
> in LibO to have also View Layout Automatic as default.
Please take into account, that the "Hide Whitespace" option is only available in single-page-view mode (see bug 98446). So I would only choose "Automatic" view by default, if there's an improvement for the "Hide Whitespace" option.
Sounds reasonable to me and personally I wouldn't care about the whitespace thing but let's depend on this issue (or someone else has a different opinion).
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.
I always like the answer no change cause of bugs that could happen. We have to much bugs.
However will close the request.