Issue 17810 - window is auto-raised whenever focus is received
Summary: window is auto-raised whenever focus is received
Status: CLOSED DUPLICATE of issue 17719
Alias: None
Product: gsl
Classification: Code
Component: code (show other issues)
Version: current
Hardware: All Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: stefan.baltzer
QA Contact: issues@gsl
URL:
Keywords: oooqa
: 18186 (view as issue list)
Depends on: 17719
Blocks:
  Show dependency tree
 
Reported: 2003-08-03 13:03 UTC by peterdaum
Modified: 2004-01-13 09:23 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description peterdaum 2003-08-03 13:03:48 UTC
Whenever a Openoffice document window receives the input focus, the window
will be automatically raised to the top of the window stack.
(This behavior started with OO 1.1x.)

Traditionally, on X-Window-based systems, it is the job of the window manager to
control the stacking order and the focus policy. On Microsoft-style systems,
a window gets the input focus with an explicit mouse click and the window with
the input focus is always on top. Most window managers for X Window allow to
set these parameters independently.

When the window manager is set up to assign the input focus to the window with
the mouse in it without automatically changing the stacking order, Openoffice
will without regard to the general system's setup still raise it's windows as
soon as the mouse enters, which makes it pretty tricky to work with several
documents at the same time.

IMHO, explicitly raising the window probably is always unnecessary, because
with a typical "click-to-focus" setup, it won't make any difference, anyway.
If there is any good reason for Openoffice's behavior, then at least there
should be some way to turn this off...
Comment 1 Unknown 2003-08-12 05:36:29 UTC
I've also encountered this problem (OOo1.1rc2 on Mandrake 9.1 using
KDE 3.1).  Here are steps to reproduce:
(1) Configure window manager (KDE) to use "focus follows mouse".
(2) Run swriter
(3) File -> New -> Text Document (this will open a second swriter window)
(4) Now whenever the mouse moves over the rear swriter window, that
window is brought to the front
Comment 2 Frank Schönheit 2003-08-19 13:46:08 UTC
changing to component "graphics system layer"
Comment 3 philipp.lohmann 2003-08-19 16:49:09 UTC
I cannot reproduce the behaviour with RC3
Comment 4 Unknown 2003-08-20 06:14:05 UTC
This problem still occurs for me with 1.1RC3.  I did a bit of
experimentation, and noticed that the problem only occurs when the
"Paragraph Styles" window is open (F11).  I could not duplicate the
problem in fvwm2 or gnome2.  I did notice however that each swriter
window seems to have its own "Paragraph Styles" window, and that when
the focus switches from swriter window A to swriter window B then the
"Paragraph Styles" for swriter window A vanishes and the "Paragraph
Styles" for swriter window B appears.  Perhaps this provokes KDE to
raise swriter window B?

So to clarify the steps to reproduce:
(1) Use KDE 3.1, configured to use "focus follows mouse"
(2) Run swriter
(3) Ensure "Paragraph Styles" window is open (toggle with F11).
(4) File -> New -> Text Document (this will open a second swriter
window with its own "Paragraph Styles" window)
(5) Again, ensure "Paragraph Styles" window is open for the second
swriter window (toggle with F11).
(6) Now whenever the mouse moves over the rear swriter window, that
window is brought to the front
Comment 5 philipp.lohmann 2003-08-20 11:46:52 UTC
I can reproduce that now. I think you're right; the transient sytlist
windows cause kwin to raise the respective document; there will not be
an easy solution to that but the newly defined behaviour in the EWHM
spec (see fredesktop.org, also issue 17719 ) may change that but only
in a future kwin implementation.
Comment 6 thorsten.martens 2003-09-02 15:52:55 UTC
*** Issue 18186 has been marked as a duplicate of this issue. ***
Comment 7 Rainer Bielefeld 2004-01-13 06:02:52 UTC
Changed to NEW because it has been reproduced by several uses in at least 2 issues.

pl, tm, you are also involved in issue 17749, don't you think this is a DUP of
the started issue 17719? I mad this issue blocks issue 17719, pls. decide 
whether you can agree with that.

Rainer
Comment 8 philipp.lohmann 2004-01-13 09:22:12 UTC
I agree, this is duplicate to issue 17719

*** This issue has been marked as a duplicate of 17719 ***
Comment 9 philipp.lohmann 2004-01-13 09:23:09 UTC
closing duplicate