Issue 43634

Summary: Page prview with focus in DB beamer doesn't show Menu toolbar
Product: Writer Reporter: runnerdav <davide.chiodi>
Component: viewingAssignee: AOO issues mailing list <issues>
Status: ACCEPTED --- QA Contact:
Severity: Trivial    
Priority: P3 CC: issues
Version: 680m80   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Issue Type: DEFECT Latest Confirmation in: ---
Developer Difficulty: ---

Description runnerdav 2005-02-27 17:00:52 UTC
Here is the behaviour: File->New->Labels - setting labels and database - New
Document - F4 to display database window. Now if I go to page preview after
having selected some records (also only one) in data grid, I get the preview,
but Menu bar disappear, 'Close preview' button is not present and after having
closed preview (via right mouse->close preview)I get my document window again
without menu bar and with dubbed database  toolbar plus some empty toolbars. Bug ?
I noticed that switching to another OOo window (i.e. first Untitled1 document
window) and than returning on altered window make menu bar to appear again (but
remain the dubbed database toolbars).
I tried with a simple two rows database made just for testing this and found
problem is easily reproducible (not tied to specific database).
Comment 1 michael.ruess 2005-02-28 07:52:53 UTC
reassigned to ES.
Comment 2 eric.savary 2005-03-07 17:58:42 UTC
ES->CD: I think we already had focus/context problems with the DB beamer
(together with floating toolbars). How to reproduce:
- New Text document
- F4 to show the DB beamer
- set the focus in the DB beamer
- File - Page Preview
-> the context is the Beamer which has no menu bar, 3 emty toolbar and not
Preview toolbar.
Even if the focus is in the Beamer, the Prview environment should correspond to
the man Window, not to the beamer.

ES->runnerdav: to come back to the normal view, double click in the document ;)
Comment 3 carsten.driesner 2005-03-11 10:55:55 UTC
cd: Confirmed.
Comment 4 carsten.driesner 2005-05-24 08:09:18 UTC
cd: We have to retarget issues due to heavy workload for OOo 2.0.1.