| Summary: | cannot close search bar using the [ESC] key | ||
|---|---|---|---|
| Product: | [Applications] konqueror | Reporter: | Paul Temple <paul.temple> |
| Component: | general | Assignee: | Konqueror Bugs <konqueror-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | andresbajotierra, finex, mss |
| Priority: | NOR | ||
| Version First Reported In: | SVN | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Paul Temple
2008-12-20 01:32:38 UTC
I'm using KDE 4.1.85 (KDE 4.2 Beta2) on Kubuntu, installed as described at http://www.kubuntu.org/news/kde-4.2-beta-2 . That being said: It's great to have the search bar in konqueror - finally! Thanks, guys, this is probably the biggest usability improvement of konqueror in the last years. Does it happen only when you've a splitted view? I guess you're talking about that Ctrl-Shift-L or Ctrl-Shift-T thing, right? When I had the problem, I didn't have split views. And now the problem is really gone, after re-assigning the key binding. So I cannot reproduce it any more. FYI: I just got the same thing in kiten: "The key sequence 'Esc' is ambiguous. Use 'Configure Shortcuts' from the 'Settings' menu to solve the ambiguity. No action will be triggered." Unassigning and re-assigning didn't fix the problem in that case. On revision 900106, the bug is still valid: when konqueror is splitted (ctrl+shift+...) CTRL+F (and "ESC" for closing the search bar) doesn't work. I still have this error message: «The key sequence 'Ctrl+F' is ambiguous. Use 'Configure Shortcuts' from the 'Settings' menu to solve the ambiguity. No action will be triggered.» In bug 176206 there's a testcase for the broken ctrl++. That one doesn't trigger but the linked page http://www.linuxjournal.com/article/6334 does (4.2-beta2). This may be related to bug 180108 (Ctrl+F ambiguous on the first time loading multiple times , too) *** This bug has been marked as a duplicate of bug 177332 *** |