Bug 182807 - Left/middle mouse click always opens link in current tab (e.g. instead of background/external) regardless of setting
Summary: Left/middle mouse click always opens link in current tab (e.g. instead of bac...
Status: RESOLVED WORKSFORME
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 166890 182948 188833 193681 202938 216258 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-02-02 00:39 UTC by monstermunch
Modified: 2016-09-25 11:07 UTC (History)
15 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description monstermunch 2009-02-02 00:39:19 UTC
Version:           1.4.0 (using 4.2.00 (KDE 4.2.0), Kubuntu packages)
Compiler:          cc
OS:                Linux (x86_64) release 2.6.27-11-generic

- open akregator
- open an article in a new tab
- switch to tab
- middle click on a link in the tab

For me, regardless of settings, the final step will always open the link in the current tab. I set middle click to "open in background" tab in settings and it doesn't make any difference. Using "open in external browser" has the same problem; it still opens in the current tab. Configuring left-click has the same problem.

Are there any workarounds for this? This really interrupts my daily news reading sessions. :-(
Comment 1 Greg M. 2009-02-10 01:10:58 UTC
Same problem here with KDE 4.2.0 on Arch Linux.

Middle-click in konqueror opens in a background tab, so it certainly would be best for akregator to do the same to preserve a consistent feel.

This feature works on KDE 3.x and I had used it whenever I wanted to read a link after finishing the current article.
Comment 2 Stephan Sokolow 2009-02-13 02:55:31 UTC
Same problem with KDE 4.2.0 in Gentoo Linux and same reasons for wanting it back.
Comment 3 monstermunch 2009-04-02 17:56:10 UTC
Same problem in 4.2.1 and 4.2.2. Is there any plans to fix this? Surely it must be simple to fix? It makes using the internal browser an incredibly slow and frustrating experience. I've switched back to the KDE 3.5 Akregator because of this. :(
Comment 4 Jonathan Marten 2009-05-05 21:28:24 UTC
*** Bug 182948 has been marked as a duplicate of this bug. ***
Comment 5 Thomas Heuving 2009-06-11 11:18:34 UTC
It works using right button and selecting "open in new tab". You then get your new tab as usual in 3.5.
Comment 6 Stephan Sokolow 2009-06-11 12:59:02 UTC
...but it still switches to the newly-created tab, making it truly painful to open a batch of links within an article.

Given my opinion of web-based applications (both performance and convenience-wise), It's really an embarassment to KDE that I've more or less dumped KMail and aKregator for GMail and Google Reader. (It means that, despite Firefox being slow and Konqueror 4.x being a pain to work with, it's not as painful as the native options)

Let's hope that, by the time KDE 5.x rolls around, there will be a GUI behaviours regression test suite to prevent a recurrence of these problems.
Comment 7 Juha Tuomala 2009-06-11 13:16:05 UTC
(In reply to comment #6)
> Given my opinion of web-based applications (both performance and
> convenience-wise), It's really an embarassment to KDE 

Yeah, this bug basically renders the Akregator useless, i've started browsing pages with standalone browser again.

Somehow in opensource model where everyone can focus to tasks they see themselves interesting, this kind of showstopper issues don't get the attention they would deserve and whole movement suffers. With this I mean that KDE4 already has all kind of bells and whistles which most of people would be happy without, but then again we failed to even fullfill the core functionality of KDE3. Yes, we all know it's coming, but it should have landed already.

I even tried to get tags enabled in bugs.kde.org so that we could get an overview to the regression items, but that request got buried since KDE uses tags for release process instead of milestones.
Comment 8 km 2009-06-12 13:53:31 UTC
*** This bug has been confirmed by popular vote. ***
Comment 9 Frédéric COIFFIER 2009-07-18 12:29:54 UTC
I confirm the bug in KDE 4.3rc2
Comment 10 Christophe Marin 2009-07-18 19:00:05 UTC
*** Bug 166890 has been marked as a duplicate of this bug. ***
Comment 11 Christophe Marin 2009-07-18 19:00:20 UTC
*** Bug 193681 has been marked as a duplicate of this bug. ***
Comment 12 monstermunch 2009-07-19 10:29:31 UTC
I can also confirm this bug is still in KDE 4.3 RC2. :-( I stopped using akregator a while ago because of this bug. I'm really confused why there is no urgency to fix such a critical interface bug.
Comment 13 m.wege 2009-11-28 22:05:30 UTC
I can confirm this bug on KDE 4.3.3. It is really annoying, would be really usefull if this is fixed.
Comment 14 m.wege 2009-11-28 22:14:29 UTC
*** Bug 188833 has been marked as a duplicate of this bug. ***
Comment 15 m.wege 2009-11-28 22:18:47 UTC
I have closed my above bug #188833, but want to transfer one additional problem from there to here: The setting "behaviour of the internal browsing component" can be missunderstood and should be fixed/ clarified as problematised there.
Comment 16 Frédéric COIFFIER 2010-01-22 15:08:38 UTC
The problem isn't corrected in KDE SC 4.4rc1.

Any hope to get it corrected in KDE SC 4.5 ?
Comment 17 Christophe Marin 2010-02-22 00:58:07 UTC
*** Bug 216258 has been marked as a duplicate of this bug. ***
Comment 18 Frédéric COIFFIER 2011-07-01 13:23:27 UTC
With KDE4.7rc1 (not tested with KDE 4.6), the problem seems to be partially solved :
 * middle-click opens a link in a new tab,
 * but the configuration isn't followed (i.e. if left click is configured to open in a new tab and middle click to open in the current tab, it doesn't work)
Comment 19 Maarten De Meyer 2012-12-10 20:25:13 UTC
*** Bug 202938 has been marked as a duplicate of this bug. ***
Comment 20 Pierre Maraval 2013-08-08 17:12:48 UTC
Kubuntu 12.04.2 LTS
KDE and Akregator 4.8.5

Default Browser rekonq, browser option in Akregator "Open with Default browser"

Akregator doesn't use the right option between "Open in new Tab", "Open n external Browser", and "Open in background Tab"

 Setting both options (left click AND middlemouse) to "Open in background Tab" makes the middlemouse option work as expected, but the left click opens in external browser.

-Options
Left click : Open in Tab 
Middlemouse : Open in Background tab
-Result
Left click : Open in external browser
Middlemouse : Open in new (activated) tab

-Options
Left click : Open in external browser
Middlemouse : Open in Background tab
-Result
Left click : Open in external browser - OK
Middlemouse : Open in new tab

-Options
Left click : Open in new tab
Middlemouse : Open in new tab
-Result
Left click : Open in external browser
Middlemouse : Open in new tab - OK


-Options
Left click : Open in Background tab
Middlemouse : Open in new tab
-Result
Left click : Open in external browser
Middlemouse : Open in new Background tab
-This setting brings the most messed up result...

-Options
Left click : Open in external browser
Middlemouse : Open in new tab
-Result
Left click : Open in external browser -OK
Middlemouse : Open in new tab -OK
-This one is perfectly OK

-Options
Left click : Open in external browser
Middlemouse : Open in external browser
-Result
Left click : Open in external browser -OK
Middlemouse : Open in external browser -OK
-This one is perfectly OK too
Comment 21 Denis Kurz 2016-09-24 19:44:43 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of akregator (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 22 M G Berberich 2016-09-25 09:42:05 UTC
seems to be fixed in 5.2.3 as far as I can tell
Comment 23 Christophe Marin 2016-09-25 11:07:23 UTC
Thanks for the feedback.