Bug 167615

Summary:	konqueror is always raised over the other window when a new url is opened
Product:	[Plasma] kwin	Reporter:	solsTiCe <solstice.dhiver>
Component:	core	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	wishlist	CC:	4ernov
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description solsTiCe 2008-07-28 20:10:54 UTC

Version:           4.1 (using KDE 4.0.98)
Installed from:    Unlisted Binary Package
OS:                Linux

that's really annoying.

the scenario is as follow:
i use akregator to read new and click on multiple links to open them in my brwoser and only after having finished go and read them in my brwoser.

but konqueror is annoying because the window is raised over akregator each time an url is opened. 
whatever i tried as advanced option or don't steal focus. it's the same. firefox is the same.

only opera behave like i want. that's why i use it. 

dont raise konqueror window. esspecially if you open a new tab for it. if you open a new windows of konqueror yees why not. but only if

Comment 1 Michael 2008-07-30 10:57:14 UTC

This sounds more like a wish than a bug. Also, i can confirm that konqueror gets raised even if it is set to "open new urls in background tabs".

Some people (including me) would really be annoyed when the browser wouldnt raise when trying to open an URL, so maybe adding an option would be the optimal solution for both. Additionaly you are able to set akregator to open everything in "background tabs", so you wont get a browser at all.

Comment 2 Thomas Lübking 2012-03-11 06:57:56 UTC

*** Bug 261404 has been marked as a duplicate of this bug. ***

Comment 3 Thomas Lübking 2012-04-10 00:29:58 UTC

from bug #167615
just checked and sth. seems broken about the timestamps, ie. the raise and/or activation is permitted because you don't seem to be active (but i typed nonsense as fast as i could)

Comment 4 Thomas Lübking 2013-07-19 13:40:25 UTC


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