Bug 158832

Summary:	html widget not focused after clicking/opening tab
Product:	[Applications] akregator	Reporter:	Will Stephenson <wstephenson>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	dev+kde, haakon+kdebugs
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Will Stephenson 2008-03-06 00:38:44 UTC

Version:            (using Devel)
Installed from:    Compiled sources

After opening a new tab or switching between tabs, the khtmlview does not have focus, and requires a click before pgup/pgdown works, for example.

Comment 1 Will Stephenson 2008-03-06 00:40:04 UTC

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

Comment 2 Haakon Nilsen 2009-03-22 16:19:03 UTC

Opening new tabs: I can not reproduce the problem on either 4.2.1 or trunk. I open a new tab, and that tab appears and has focus and I can use up/down/pgup/pgdown. Seems to work in all cases.

Switching between tabs: It doesn't look like you can do this with the keyboard, only with the mouse. When you press a tab to switch to it, it seems like the tab has focus and not the khtmlview (or the articlelistview), so an extra click is indeed required. There is some focus code in TabWidget::slotSelectFrame(int), but it's only called when new tabs are created (which explains why that works) and not when the user switches tabs.

Comment 3 Frank Steinmetzger 2013-06-20 22:55:22 UTC

I oftentimes encounter this bug while reading the comments forum of news sites (such as heise.de). I open each thread of interest in a new tab and then switch to it. Sometimes when I press space to scroll the view, instead the background task widget in Kontact's bottom right corner is enabled. So I start seeing progress bars for downloads, but there is NO button to disable it again. KDE 4.10.4 here on Gentoo.

Comment 4 Denis Kurz 2016-09-24 19:41:04 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 5 Denis Kurz 2017-01-07 22:27:13 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.