Issue 96290 - Documents should remember navigator, styles and formattings state
Summary: Documents should remember navigator, styles and formattings state
Alias: None
Product: General
Classification: Code
Component: ui (show other issues)
Version: OOO300m9
Hardware: All All
: P3 Trivial with 4 votes (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
: 104863 111344 (view as issue list)
Depends on:
Reported: 2008-11-17 23:59 UTC by graneezle
Modified: 2013-02-07 22:35 UTC (History)
1 user (show)

See Also:
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description graneezle 2008-11-17 23:59:00 UTC
Each document should remember the state of the navigator (i.e. whether or not it
is displayed, where it is displayed, what options are selected, etc.) when that
document is closed and automatically go back to that state when reopened.

I work with many Writer and Calc documents on a laptop with a 12" screen. For
some documents, e.g. outlines, I always want to show the navigator docked at
left. For others, e.g. spreadsheets that take up the whole width of the screen,
I never want to show the navigator at all. At present, if I have a Writer
document open with the navigator, then go to Calc and open a spreadsheet, the
navigator automatically appears. If I can't see all my data (frequently the
case), I have to close the navigator manually. Done once a week, this is not a
problem; done a dozen times a day, as I do, it gets kind of annoying.

N.B. I have put this issue under Writer, but really it applies to all OO
applications that use the navigator.
Comment 1 michael.ruess 2008-11-19 13:46:41 UTC
Useful thing, could be implemented together with issue 84917.
Comment 2 eric.savary 2010-05-03 15:22:45 UTC
... For each document and/or by application, see issue 104863
... Also this of course applies to every float pane (i.e. Styles and formattings).
Comment 3 eric.savary 2010-05-03 15:25:28 UTC
*** Issue 104863 has been marked as a duplicate of this issue. ***
Comment 4 eric.savary 2010-05-03 15:27:00 UTC
*** Issue 111344 has been marked as a duplicate of this issue. ***