A common usage scenario is to place two documents side by side in two Writer windows. The problem with this is that the document becomes too small: a workaround is to zoom, remove rulers, and use Web Layout. However in some documents the layout is very important, and therefore Web Layout cannot be used.
I propose a new view mode in which the rulers and page margins are not shown, and the editable part of the page is automatically zoomed to the full width of the non-chrome Writer window.
Created attachment 47425 [details]
A proposed mockup of the feature in action.
This screenshot is a mockup of the proposed feature in action. The proposed feature is on the left, a regular Writer window is on the right.
Created attachment 47426 [details]
The original document layout (current implementation) from which the proposed screenshot was derived.
[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
This feature request is still valid for the latest development version
As I can understand:
"Option to disable show on screen rulers ans part of page outside page margins"
this differs from pressing Ctrl-Shift-J by this: toolbars and menu need to be on screen.
No, Sasha, this RFE has nothing to do with fullscreen. This RFE requests a view mode in which the rulers and page margins are not shown, and the editable part of the page is automatically zoomed to the maximum possible without having a horizontal scrollbar appear.
Please read this message in its entirety before responding.
Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed.
If you have time please do the following:
1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer).
2) If it is present please leave a comment telling us what version of LibreOffice and your operating system.
3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System
Please DO NOT
1) Update the version field
2) Reply via email (please reply directly on the bug tracker)
3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case)
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link:
There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/.
Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material
remains a valid enhancement
*** Bug 123523 has been marked as a duplicate of this bug. ***
attachment 149353 [details] and attachment 149354 [details] from duplicate bug 123523 show intent that the set margin should be excluded in rendering the document canvas in single and multi-page views.
As noted, the current hide-whitespace UNO command is only functional in single-page view. Expanding to include the multi-page view seems appropriate.
*** Bug 96130 has been marked as a duplicate of this bug. ***
Switching rulers on/off and hiding the page margins sounds not like a view mode to me. (You can disable the rulers and hide whitespace via the View menu). The "view mode" reminds me rather on the print preview.
The actual scenario here is to visually compare documents with a special side-by-side view that is not a multidocument interface.
Use case are also commented on in the duplicates, and this new "view" requires more than just hiding the rulers and page margins. The "remove white-space" command is not sufficient as it only removes the top and bottom margins when document extends to multiple pages, but could be tweaked.
The view needed, including ability to Zoom larger or smaller, is to _display_ just the _editable_ canvas area--dropping out all 4 margins (and header/footers). Rulers would go, Slide bars remain obviously. Header/Footers controls would go inactive, and not be considered for movements of the canvas.
Imagine most behavior would be the same--just the area of the "view" would be the text held inside the margins. Rather than our standard view defaults which are:
width of interior text area + l-margin + r-margin = full frame width
height of the interior text area + header + t-margin + footer + b-margin = frame height.
Would become a view
width of interior text area = full frame width
height of interior text area = full frame height
It could be linked to a button, like current "remove white-space", and possibly also added to the View modes on the status bar.
I'm totally in for making the "hide whitespace" function also affecting the left/right margins. But I don't see switching UI elements on/off, or collapsing it, as a special "view". That would rather be a MUFFIN thing and perfectly suited for an extension.
Regarding use cases, for example bug 123523 is not talking about a workflow. It could be "I want to have more space to read documents in full size on my small screen" or a bit more far fetched "I want to use large margins but not see it while editing". As a WYSIWYG editor this is going to be out of scope. We should be very carefully with keeping focus not working on the swiss-army-knife.
What makes sense to me is the workflow "I want to visually compare documents" and we have to consider special solutions (not saying hide whitespace etc. is off-topic in this mode).
(In reply to Heiko Tietze from comment #14)
『Hide blank』=『Dark mode』
(In reply to V Stuart Foote from comment #9)
> *** Bug 123523 has been marked as a duplicate of this bug. ***
"37817" is different from "123523".
『37817』→『No』 horizontal scroll.
『123523』→『Have』 horizontal scroll.
Please change back.
(In reply to 和尚蟹 from comment #16)
"123523" → When "display 600%", "have" a horizontal scroll.
(In reply to 和尚蟹 from comment #16)
> (In reply to V Stuart Foote from comment #9)
> "37817" is different from "123523".
> 『37817』→『No』 horizontal scroll.
> 『123523』→『Have』 horizontal scroll.
> Please change back.
It is a dupe with *exactly* the same functional and development issues.
The "no horizontal scroll" here is an oblique reference to how the current zoom to "Optimal View" includes the left and right margins and activates a scroll bar.
This mode, hiding the white space of the margins, would still require the scroll bar, just not at its default full zoom, and the scroll would only affect what is displayed of the document canvas.
Also, what you call Dark mode is not the correct usage. Dark mode is a theme issue becoming common with macOS Mojave and Windows 10 app design (long available on Linux desktops).
(In reply to V Stuart Foote from comment #18)
> It is a dupe with *exactly* the same functional and development issues.
> The "no horizontal scroll" here is an oblique reference to how the current
> zoom to "Optimal View" includes the left and right margins and activates a
> scroll bar.
> This mode, hiding the white space of the margins, would still require the
> scroll bar, just not at its default full zoom, and the scroll would only
> affect what is displayed of the document canvas.
After the theme has been changed, there is no problem.
> Also, what you call Dark mode is not the correct usage. Dark mode is a theme
> issue becoming common with macOS Mojave and Windows 10 app design (long
> available on Linux desktops).
I don't know how to express it, so using "Dark mode" to express it means reducing the meaning of "white".