Bug 188833 - articles can not be opened in tabs via mouse click
Summary: articles can not be opened in tabs via mouse click
Status: RESOLVED DUPLICATE of bug 182807
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Unspecified
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-04 21:39 UTC by m.wege
Modified: 2009-11-28 22:14 UTC (History)
3 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 m.wege 2009-04-04 21:39:34 UTC
Version:            (using KDE 4.2.2)
Installed from:    Ubuntu Packages

When I want to read an article in a tab and open it via a mouse click, the tab does not open. Nothing happens. I have reviewied the settings, even deleted all the config files. The problem remains. New tabs can be still be open from the menue or via right click and the context menu. But still this is a serious bug, because it takes away one of the main functionalities.

This bug was also reported downstream @ Kubuntu
https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/355301
Comment 1 Haakon Nilsen 2009-04-04 23:02:38 UTC
I cannot reproduce this, but perhaps I don't understand the issue correctly. Here's what I do (in Akregator 1.4.2 / KDE 4.2.2):

* In Settings -> Configure Akregator -> Browser, make sure "Left mouse click" is set to "Open in Tab"
* Select a feed
* Select an article from the feed
* Press the "Complete Story" link from the summary

The article is now opened in a new tab, as expected.

Can you confirm that these steps does NOT open a tab for you?
Comment 2 m.wege 2009-04-04 23:18:15 UTC
Yes, I can confirm that this is the exact problem. I has been there through the whole KDE4 series, but have to admit I have failed to report it until know since I am still running KDE4 (4.2.2 know) in a test installation. I have deleted /.kde/share/apps/akregator and /.kde/share/config/akregatorrc before reporting this just to make shure I did not continue with some old bad settings. But it did not fix it. I have thinkpad with a trackpoint. But normally this does not cause any problems. May be in this case?
Comment 3 m.wege 2009-04-05 00:09:55 UTC
Wait, I have to correct myself. The exact way to reproduce it is:
- set: Behaviour on pressing on the left mouse button to "open new tab" or "open new tab in the background"
- do exactly that, no new tab will open
- if you configure the same behaviour for the middle mouse button it will work.
Comment 4 Haakon Nilsen 2009-04-05 14:36:20 UTC
Well, this works for me. Both left and middle buttons work for both open in tab, open in background tab, and open in external browser. Does external browser work for you?
Comment 5 m.wege 2009-04-05 14:47:17 UTC
In general the setting for the left mouse button only reacts on a double click, the middle button accepts a single click. When I configure the left mouse button for open in tab/background tab, a double click opens the article in the external browser. If set it to open in the external browser, it opens it on a double click. A single click on the left button in all cases brings the reduced for of the article to the window below.
Comment 6 Teemu Rytilahti 2009-05-24 03:27:40 UTC
If I understood correctly, you're talking about having one click on the article list? The settings in the configuration window about the mouse buttons are about clicking on links on that "reduced" internal viewer.
Comment 7 Mads Bondo Dydensborg 2009-06-04 09:58:37 UTC
I think to many users it has not been clear, that the settings are for the "article list" only. I thought they controlled akregator in general.

The settings - as applied to the list view and the minipage for previewing - works for me.

But, bug 166890 does apply to me; whatever I do, left and middleclick on a the htmlview in a tab, that is, when showing a "real" page, just opens in that tab. I would expect middleclick to open in a new tab (as konqueror do).
Comment 8 m.wege 2009-11-28 22:14:29 UTC
I agree with comment #7. I did not know for what exactly this setting would do. It would be good to clarify that and/or to create a setting which also means the viewer component. But from the perspektive what was originally my problem, it appears that my bug is a duplicate of #166890 or now #182807. I will add the problem about the setting to that bug.

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