Bug 137153 - VIEWING: Navigator sidebar not dockable
Summary: VIEWING: Navigator sidebar not dockable
Status: RESOLVED DUPLICATE of bug 113416
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.0.1.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: needsUXEval
Depends on:
Blocks:
 
Reported: 2020-09-30 09:42 UTC by Christian Lehmann
Modified: 2020-10-05 09:40 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 Christian Lehmann 2020-09-30 09:42:17 UTC
Description:
I can dock the Styles sidebar as expected. I can exchange it for the Navigator bar. (By this procedure, I can even, uselessly, have a Navigator sidebar and a floating Navigator simultaneously.) I can drag it from the right side to the left side of the editor window. What I _cannot_ do is have the Navigator bar on the left side and the Styles bar on the right side of the editor window. The current help text (https://help.libreoffice.org/7.0/en-US/text/swriter/guide/resize_navigator.html?&DbPAR=WRITER&System=UNIX) lies about this: "To dock or undock the Navigator or the Styles window, hold down the Ctrl key and double-click on a gray area in the window. Alternatively, press Ctrl+Shift+F10." These actions do not work.

Steps to Reproduce:
1. Open a document in Writer.
2. F5.
3. CTRL-doubleclick or CTRL-SHIFT-F10 on a gray area in the Navigator bar.

Actual Results:
CTRL-doubleclick: Nothing.
CTRL-SHIFT-F10: Context menu for headings pops up.

Expected Results:
The Navigator bar should dock at that side of the editor window where it has been floating.


Reproducible: Always


User Profile Reset: No



Additional Info:
Alternatively, the following would be a useful procedure: Drag the sidebar to the desired position, and it snaps in (as it is the case with other toolbars).

This is a regression. Docking the Navigator bar on the left side of the window while keeping the Style bar open on the right side used to be possible in earlier LO versions.
Comment 1 Dieter 2020-09-30 10:33:05 UTC
I can't confirm it with

Version: 7.0.1.2 (x64)
Build ID: 7cbcfc562f6eb6708b5ff7d7397325de9e764452
CPU threads: 4; OS: Windows 10.0 Build 19041; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: en-GB
Calc: threaded

Additional information:
If cursor is somewhere within the document Ctrl+Shift+F10 doesn't work (nothing happens). You have to click somewhere in the navigator bar before.
Ctrl + double Click only works, if pointer is somewhere within navigator bar.

Chjristian, are you able to confirm this?

So I can't assess, if this is a bug or a lack of information in the help text.
Comment 2 Christian Lehmann 2020-09-30 10:57:00 UTC
I did click where I was supposed to click, as explained in my description.
I confess I was surprised myself to be confronted with this bug, because I had worked with version 7.0.1 before, and it worked well. That was on Ubuntu, Gnome desktop. The current installation is:

Version: 7.0.1.2
Build ID: 00(Build:2)
CPU threads: 12; OS: Linux 5.3; UI render: default; VCL: gtk3
Locale: de-DE (de_DE.UTF-8); UI: en-US
Calc: threaded

on OpenSuse Leap 15.2, but still using Gnome desktop.
Comment 3 Dieter 2020-09-30 11:42:42 UTC
(In reply to Christian Lehmann from comment #2)
> I did click where I was supposed to click, as explained in my description.

Sure, but that doesn't answer my question, because it depends on where the cursor / the pointer is locatet while you click. And I couldn't find any information about it in you bug report.
Comment 4 Christian Lehmann 2020-09-30 11:55:36 UTC
Let's see whether I understand what you mean:
If I click in the Navigator sidebar on any point that has neither text nor symbols (in particular, a gray area), nothing happens. If I click, e.g., on a section heading, it gets a blue background. If I click on the head bar, its gray becomes more intensive.

The pointer then stays where I left it in the sidebar until I move it into a gray area to execute the prescribed clicks.
Comment 5 Christian Lehmann 2020-09-30 13:19:01 UTC
Let me add another observation on a weird behavior of the cursor if more than one window for LO Writer is open:

I have a document in the main window with a floating Navigator sidebar and have a second window on the same document. In the main window, I click 'Window' - 'Document name:2'. The text cursor shows up in the editor pane of the secondary window.
I now click in the editor pane of the main window. The Navigator - apparently shared between the two windows on the same document - is rewritten, and blue highlighting shifts to the relevant section heading. However, the text cursor is not in the editing pane where I clicked; it is nowhere. I have to click once more in the editor pane in order to make it available there.

I have already been reproached in these circles for adding what appeared to them as a different bug. However, I mention it here because it seems to be related to Bug 137153.
Comment 6 Dieter 2020-09-30 14:55:06 UTC
(In reply to Christian Lehmann from comment #4)
> Let's see whether I understand what you mean:

Perhaps I wasn't clear enough. Let me try again.

1. Open a new document
2. Strg+F5 open sidebar on the right; choose styles tab
3. F5 opens floating navigator => Focus is on navigator
4. Ctrl+Shift+F10 => navigator is docked on left side

O. K.

5. Ctrl+Shift+F10 => floating navigator
6. click in first paragraph => focus is in paragraph
7. Ctrl+Shift+F10 => nothing happens

Perhaps a bug or a lack of information in documentation

8. Ctrl+Double click on a grey area within the floating navigator => O. K.
Comment 7 Christian Lehmann 2020-09-30 15:37:15 UTC
At first try, the result of following your instructions was negative as before.
I restarted the system and tried again; and like a miracle, your predictions now came true.
It still looks like a bug, although one hard to pin down.
I hope to report on irregular cursor behavior (also observed by other users, by the way) on the next occasion.
Comment 8 Dieter 2020-10-01 05:56:48 UTC
(In reply to Christian Lehmann from comment #7)
> It still looks like a bug, although one hard to pin down.

Let's ask design-team for decision
cc: Design-Team
Comment 9 Heiko Tietze 2020-10-05 09:40:38 UTC

*** This bug has been marked as a duplicate of bug 113416 ***