Issue 122816

Summary: [sidebar] WRITER does not keep state of 'Content View' in Navigator
Product: General Reporter: Rainer Bielefeld <rainerbielefeld_ooo_qa>
Component: uiAssignee: AOO issues mailing list <issues>
Status: CONFIRMED --- QA Contact:
Severity: Normal    
Priority: P3 CC: issues
Version: 4.0.0   
Target Milestone: ---   
Hardware: All   
OS: Windows 7   
See Also:
Issue Type: DEFECT Latest Confirmation in: ---
Developer Difficulty: ---
Description Flags
Sample Document none

Description Rainer Bielefeld 2013-07-24 04:29:58 UTC
Created attachment 81128 [details]
Sample Document

Steps how to reproduce Reproducible with  "AOO 4.0.0-Dev – English UI / German locale -  [AOO400m3(Build:9702)  -  Rev. 1505643  2013-07-23]" on German WIN7 Home Premium (64bit)", own separate user profile:

1. From AOO Start Center open attached Writer sample document
2. Meneu 'View -> Sidebar' to activate Sidebar if invisible
3. In Sidebar Click compass for The Navigator deck
   > You see lots of entries for headings, tables, sections, ...
4. Below Sidebar Deck heading "Navigator" click icon 'Content View'
   > Only Headings will stay visible in Navigator
5. Activate "Properties" Deck in sidebar by clicking that icon
   In the right margin of the sidebar
   > Properties Deck appears
6. In Sidebar Click compass for The Navigator deck
   > Navigator Deck appears
   Expected: Only Heading entries visible
   Actual: again all entries for headings, tables, sections, ...

a) It's not completely the same like switching between the decks, but if you
   switch on / off / on Navigator with the icon in the Standard Toolbar the
   latest  Content View persists
b) I think generally a deck should reappear with the latest view it had before
   user changed to an other deck
c) The Original report for this was in LibO Bugzilla 
   FDO Bug#67230 - Sidebar does not keep state of Content View in Navigator 
   By user "David"
Comment 1 Ariel Constenla-Haile 2013-07-24 04:56:19 UTC
This looks like duplicated of Bug 122406
Comment 2 Rainer Bielefeld 2013-07-24 08:40:08 UTC
The very general description of Bug 122406 at least also could be used here. The question is what the optimum proceeding will be. If it is likely that there is a common root of all those "panel looks different after switched to other deck and back" we can make them all DUPs of Bug 122406.

But I think there will appear several unlovely effects with very different roots, where I would prefer to see them related - or blocking a tracking bug. So each can be fixed separately and there is no danger that 1 problem will be forgotten.