Bug Hunting Session
Bug 44804 - UI: Navigating Headings using the Navigator
Summary: UI: Navigating Headings using the Navigator
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.4.4 release
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-15 07:22 UTC by contact
Modified: 2012-07-10 12:01 UTC (History)
3 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 contact 2012-01-15 07:22:38 UTC
Problem description: 
Double click on heading that has sub-headings in the Navigator causes tree to collapse/expand, even if you just want to get to the heading.

Steps to reproduce:
1. Create a file large enough you want to use the Navigator
2. Put some Headings 1 and 2 in there
3. Go to a Heading 1 that has sub-Headings by double clicking on it in the Navigator

Current behavior:
Tree collapses if it is expanded or expands if it is collapsed.

Expected behavior:
I just want to navigate the file. One possibility would be to make a single click the default "I want to go there"-command (this would be my preferred solution), or to prevent the tree from collapsing/expanding at a double click (the user would have to use the "+"/"-" buttons to do that).

Platform (if different from the browser): 
              
Browser: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0.1) Gecko/20100101 Firefox/9.0.1
Comment 1 Jean-Baptiste Faure 2012-01-15 14:24:49 UTC
I do not reproduce with LO 3.5.0 beta3+ nor LO 3.4.4 on Ubuntu 11.10 x86_64 (Gnome-Shell). The behavior of the double-click is, for me, go there *and* expand/collapse this level of the tree.
I have nothing to say against that.

Best regards. JBF
Comment 2 sasha.libreoffice 2012-05-08 04:33:06 UTC
Not reproduced also in 3.5.3 on Windows 7
Comment 3 bfoman (inactive) 2012-07-10 12:01:42 UTC
Please check if this bug is reproducible with the latest stable release and reopen if needed.