Bug 306432

Summary: Opening a new tab from KHTML no longer puts the focus on the address bar
Product: [Applications] konqueror Reporter: Sami Boukortt <sami>
Component: khtml partAssignee: Konqueror Developers <konq-bugs>
Status: RESOLVED FIXED    
Severity: normal CC: adawit, b.buschinski, bugs.kde.org, kde
Priority: NOR Keywords: regression, usability
Version: 4.9.1   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: https://projects.kde.org/projects/kde/kde-baseapps/repository/revisions/5fa3dbc49f8cac8253e198298948832ca7d38674 Version Fixed In: 4.9.2

Description Sami Boukortt 2012-09-08 00:48:06 UTC 
In Konqueror 4.9.1, opening a new tab from a page opened in KHTML does not give the focus to the address bar anymore. If I recall correctly, it worked fine in 4.9.0 and before.

The problem does not seem to occur when the current page is rendered by KWebKit.

Reproducible: Always

Steps to Reproduce:
1. Make sure that the current page is rendered via KHTML.
2. Open a new tab using Ctrl+T (or the shortcut assigned to that action if different from Ctrl+T).
Actual Results:  
After the tab is created, the focus is not on the address bar. One has to click it or press F6 or Ctrl+L in order to be able to enter an URI.

Expected Results:  
After the tab is created, the focus is on the address bar and an URI can be entered immediately.

Though I am not sure about this, it seems to me that this behavior is a regression from Konqueror and KHTML 4.9.0.
Comment 1 Sami Boukortt 2012-09-08 16:04:24 UTC 
The behavior was, indeed, correct in 4.9.0. I have just tried to reproduce the bug on a machine that had not been upgraded yet, with no success.

It is a regression.
Comment 3 Dawit Alemayehu 2012-09-09 14:20:26 UTC 
(In reply to comment #2)
> Current suspect is
> https://projects.kde.org/projects/kde/kde-baseapps/repository/revisions/
> 55c0f6baf97a07d1ee03a6a0523f9d4ea3ad40a3

This has already been fixed, but unfortunately the fix came after the 4.9.1 release.
Comment 4 Dawit Alemayehu 2012-09-13 12:53:32 UTC 
*** Bug 306714 has been marked as a duplicate of this bug. ***