https://issues.apache.org/ooo/show_bug.cgi?id=122816

            Bug ID: 122816
        Issue Type: DEFECT
           Summary: [sidebar] WRITER does not keep state of 'Content View'
                    in Navigator
           Product: General
           Version: AOO 4.0.0
          Hardware: All
                OS: All
            Status: CONFIRMED
          Severity: normal
          Priority: P3
         Component: ui
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected]

Created attachment 81128
  --> https://issues.apache.org/ooo/attachment.cgi?id=81128&action=edit
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"

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.

Reply via email to