Bug 202370 - closing tab sets focus to search instead of content
Summary: closing tab sets focus to search instead of content
Status: RESOLVED FIXED
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: 5.5.2
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 219146 319817 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-08-03 09:41 UTC by Frank Niethardt
Modified: 2021-03-17 22:23 UTC (History)
8 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 Frank Niethardt 2009-08-03 09:41:41 UTC
Version:           1.5.0 (using Devel)
OS:                Linux
Installed from:    Compiled sources

read some blog entry
click on a link in it
close tab (ctrl-w)
-> cursor blinks in search bar

should be in content, so that you can scroll or press + for next entry...

this changed since RC1 I guess
Comment 1 frank 2009-11-10 13:43:38 UTC
nobody want to fix this? it's annoying having to remember to hit the tab key after closing a tab in order to get the '+' shortcut working...
Comment 2 Christophe Marin 2009-11-16 01:04:36 UTC
I can't reproduce the issue with trunk. 

When I close the tab, '+' works as expected.
Comment 3 Frank Niethardt 2009-11-16 01:16:07 UTC
Have you used the keyboard shortcut or the mouse? It does work as expected when using the mouse, but not when using keyboard shortcut.

In 4.3.3 (1.5.3) the bug is still present.
Comment 4 Frank Niethardt 2010-01-03 19:45:08 UTC
And in 4.4 beta 2, too.

I was digging in the code today, made a diff between 4.2 and 4.3. The only related difference, I can see, is, that before rev 944029 the tabsClose button had the ShortCut Ctrl-W. This was removed in this commit.

Therefore I think, that IMHO before the commit Ctrl-W triggered the tabsClose button and so the effects are identical to clicking on it. After that commit the triggered action differ. Clicking on the tabsClose button calls TabWidget::slotRemoveCurrentFrame() and pressing Ctrl-W calls TabWidget::slotCloseTab(). 

I don't understand the code deep enough to say in what way these differences have influence of the focus of the searchbar.

HTH
Comment 5 Christophe Marin 2010-02-22 01:15:03 UTC
*** Bug 219146 has been marked as a duplicate of this bug. ***
Comment 6 RSB 2011-02-09 22:58:39 UTC
The bug is still present in the new KDEpim Suite 4.6 beta4 (Akregator 1.6.0).
It's really annoying that  after closing all tabs (with Strg/Ctrl +w) you have to pres tab twice to get to the article list
Comment 7 Christophe Marin 2011-04-08 18:02:28 UTC
and I'm still unable to reproduce with kdepim master.
Comment 8 Graeme Hewson 2012-05-18 16:53:04 UTC
The bug is still present in 4.8.2 and 4.8.3. I'm using Kubuntu 12.04, recently with the KDE 4.8.3 Personal Package Archive installed.

This happens whether Akregator is run standalone or embedded within Kontact.

I have F12 set up as a shortcut for Close Tab in Akregator within Kontact (this isn't configured in standalone Akregator, which seems to have its own setup). Whether I use F12 or Ctrl+W, the focus always goes to the Search bar.
Comment 9 Christophe Marin 2013-05-18 09:46:55 UTC
*** Bug 319817 has been marked as a duplicate of this bug. ***
Comment 10 Frank Steinmetzger 2013-06-20 22:56:11 UTC
My use case is using j, k and space to scroll the article. But when the focus sits in the search field, then of course I start filtering for j, k or space. This clears the selection in the article list (for articles that I want to delete in one go) and -- once I cleared the filter field -- I have to scroll the article list back to where I was before. KDE 4.10.4 on Gentoo.
Comment 11 Denis Kurz 2016-09-24 19:38:56 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 12 Graeme Hewson 2016-09-26 14:52:11 UTC
I confirm the bug is still present in Akgregator 5.1.3.
Comment 13 Denis Kurz 2016-09-26 18:00:17 UTC
Graeme, thanks for your feedback
Comment 14 Ricardo J. Barberis 2016-12-04 22:35:24 UTC
Still present in akregator 5.3.0
Comment 15 Steve Goodey 2017-07-11 12:00:27 UTC
Referring to Comment 3, "It does work as expected when using the mouse, but not when using keyboard shortcut."

I have the same problem even using the mouse. Close tab using mouse, cursor blinks in search field. Have to click a different article to get cursor out of search field.

Steve.
Comment 16 Ricardo J. Barberis 2017-07-14 17:45:59 UTC
Bug still present in Akregator 5.5.2 (KDE Frameworks 5.35.0, Qt 5.7.1)
Comment 17 frank 2019-02-22 16:21:14 UTC
seems fixed to me (v5.10.2)
Comment 18 Ricardo J. Barberis 2021-03-17 16:13:01 UTC
Confirmed fixed as of Akregator 5.16.3 (20.12.3).