Bug 206591 - Disable Focus Steeling Prevention for "Save as" Dialog
Summary: Disable Focus Steeling Prevention for "Save as" Dialog
Status: RESOLVED DUPLICATE of bug 110543
Alias: None
Product: kwin
Classification: Plasma
Component: rules (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-07 09:00 UTC by patrick.schwalm
Modified: 2022-04-22 19:36 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description patrick.schwalm 2009-09-07 09:00:21 UTC
Version:            (using KDE 4.3.1)
OS:                Linux
Installed from:    Unlisted Binary Package

Hi all,

my idea is to diable Focus Steeling Prevention for the Save as Dialog System-Wide.

An example where this would be helpful can be drawn by using firefox/flashgot/kget.

When I click on a link and choose kget to download the file, kgets "Save as" window will open, but behind the maximized firefox window...

You need to go to the task list and raise this dialog to save the file... 

I just told kwin not to use focus stelling prevention for this type of dialogs and now it is much more comfortable to use kget.

We could integrate this by default, I think the save as dailog should never be prevented from steeling focus, it should be its intention to stell the focus and say" Hi.... save your file or its gone!!"

Sorry for my bad english. 

I hope you can understand what i wanted to tell...
Comment 1 Thomas Lübking 2012-04-22 14:58:05 UTC
This doesn't work (easily) because the only available determining hint is the title string, which fails on localization.

Possible solutions:
a) fix application to get the dialog transient for the "effective" client leader
b) add a window role property to the open / save dialogs for cross i18n determination
c) improve focus stealing prevention (see big #110543)
Comment 2 Nate Graham 2022-04-22 19:36:56 UTC

*** This bug has been marked as a duplicate of bug 110543 ***