Bug 119909 - LO Writer 6.1.1.2 no longer allows to hide page break in normal view
Summary: LO Writer 6.1.1.2 no longer allows to hide page break in normal view
Status: RESOLVED NOTABUG
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.1.1.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-09-16 19:18 UTC by Enrique Perez-Terron
Modified: 2018-09-18 07:00 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Enrique Perez-Terron 2018-09-16 19:18:20 UTC
Description:
Since I installed v. 6.1.1, in Writer, I hover the mouse over the gap between pages in normal view, but no clickable handle to contract the page break appears. 64-bit version. This happened after opening a document previously saved with 5.4.6.2 32-bit version (saved to Dropbox using a different computer with 32-bit Windows).

Steps to Reproduce:
1. Create a document in Writer, save as odt. (Maybe it must be saved using an earlier version of Writer, in my case 5.4.6.2 32-bit
2. Open using Writer 6.1.1.2 64-bit under Windows 10
3. Hover the mouse in the gap between to pages.

Actual Results:
The mouse takes the shape of an arrow

Expected Results:
The mouse pointer should take the shape of two horizontal bars, indicating that if you click, the footer and header area will be hidden and only a dashed line will indicate the page break. 


Reproducible: Always


User Profile Reset: No



Additional Info:
Comment 1 Dieter 2018-09-16 19:54:22 UTC
I'm not sure, but I assume, that your bug is about hiding whitespace. So if you have the horizontal bar, and you click, you hide whitespace (Menu: View => "Hide Whitespace" is enabled).

But everything works as expected in

Version: 6.2.0.0.alpha0+ (x64)
Build ID: 414ef6cb187dd3bbcc917dbedf3c0c1cc8668f60
CPU threads: 4; OS: Windows 10.0; UI render: GL; 
TinderBox: Win-x86_64@42, Branch:master, Time: 2018-08-21_00:13:04
Locale: en-US (de_DE); Calc: CL

Please correct me, if I misunderstood something.
Comment 2 Enrique Perez-Terron 2018-09-16 20:37:55 UTC
Yes, it is about hiding vertical white space.

I just installed version 6.1.1.2 on the 332-bit computer too, typed into a new document until it had two pages, and hovered the mouse over the gap between the pages. As with the case reported, there was no possibility to click and hide the white space. I then went to the "View" menu and found the option "Hide Whitespace" greyed out.
Comment 3 Dieter 2018-09-16 21:06:15 UTC
Please check, if your view layout is "automatic" (view => zoom => zoom) In this case "hide whitespace" is not available. See bug 108335 and bug 98446.
Comment 4 Enrique Perez-Terron 2018-09-17 21:58:50 UTC
Yes, I had "Automatic" zoom. I selected "Single page" instead, and now "Hide whitespace" is available in the menu. Selecting this menu entry did what I wanted. :)

I also tried to use the mouse, and as soon as I remembered to double-click, that worked too.

Should this be closed as RESOLVED? Or should it be reclassified as a usability problem because it is hard for users to know how to achieve what they want? 

Perhaps it should be possible to access "Hide whitespace" even in Automatic mode, and if hiding whitespace is incompatible with the functionality of automatic zoom, automatic zoom should be automatically deselected when the user activates "Hide whitespace".

I also question if it should be enough to click once in the gap between pages. What is the advantage of binding this function to a double-click?
Comment 5 Jean-Baptiste Faure 2018-09-18 07:00:57 UTC
(In reply to Enrique Perez-Terron from comment #4)
> Yes, I had "Automatic" zoom. I selected "Single page" instead, and now "Hide
> whitespace" is available in the menu. Selecting this menu entry did what I
> wanted. :)
> 
> I also tried to use the mouse, and as soon as I remembered to double-click,
> that worked too.
> 
> Should this be closed as RESOLVED? Or should it be reclassified as a
> usability problem because it is hard for users to know how to achieve what
> they want? 

So closing as NotABug.
Your question is part of bug 108335.

Best regards. JBF