Bug 998046 - libreoffice-base windows for a table, query, or form always open maximized
Summary: libreoffice-base windows for a table, query, or form always open maximized
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: libreoffice
Version: 19
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-16 20:27 UTC by Craig Goodyear
Modified: 2013-09-02 19:09 UTC (History)
6 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2013-09-02 19:09:46 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Craig Goodyear 2013-08-16 20:27:15 UTC 
Description of problem:
All windows opened from within libreoffice-base to show a table, query, or 
form are opened in the maximized state.  It does not make any difference what
state the window was in when saved during the edit process.

Version-Release number of selected component (if applicable):
libreoffice-base-4.1.0.4-6.fc19.x86_64

How reproducible:
Every time a window is opened.

Steps to Reproduce:
1. create a table, query, or form in libreoffice-base
2. open the table, query, or form to view the results

Actual results:
window opens maximized

Expected results:
window opens with the size and state of the last edit

Additional info:
Comment 1 Caolan McNamara 2013-08-20 13:43:11 UTC 
I think it has always been like this, right ?
Comment 2 Caolan McNamara 2013-08-20 19:31:23 UTC 
Fixed now as http://cgit.freedesktop.org/libreoffice/core/commit/?id=c3164e42dcdf879ed53e235db13f498eb730bae9

will be in >= 4.1.1.1-3
Comment 3 Craig Goodyear 2013-08-20 20:12:48 UTC 
(In reply to Caolan McNamara from comment #1)
> I think it has always been like this, right ?

No, it wasn't this way in Fedora 18 running libreoffice 3.6.
Comment 4 Craig Goodyear 2013-09-02 17:08:30 UTC 
The update to libreoffice version 4.1.1.2-2.fc19.x86_64 has solved this problem.
Note You need to log in before you can comment on or make changes to this bug.