Bug 84217 - [testcase] Tab key should select entries in text completion of text fields
Summary: [testcase] Tab key should select entries in text completion of text fields
Status: RESOLVED WORKSFORME
Alias: None
Product: konqueror
Classification: Applications
Component: khtml forms (show other bugs)
Version: 4.8.4
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-06-29 18:27 UTC by MaxAuthority
Modified: 2023-01-30 05:06 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
testcase (403 bytes, text/html)
2008-04-06 08:20 UTC, Michael Leupold
Details

Note You need to log in before you can comment on or make changes to this bug.
Description MaxAuthority 2004-06-29 18:27:03 UTC
Version:           3.2.90 (using KDE 3.2.90 (3.3 alpha1, CVS >= 20040522), Gentoo)
Compiler:          gcc version 3.3.2 20031218 (Gentoo Linux 3.3.2-r5, propolice-3.3-7)
OS:                Linux (i686) release 2.6.3-rc2-mm1

When I enter some text in form fields which I filled in before, my old entries are suggestion in a "Dropdown List" text completion.

This is a very good thing, but normally with these completion boxes I can press the Tab key to select the first entry of the completion box. However, in Konqueror I have to hit the Down-Arrow key, which is far more away from the normal hand positions and also inconsistent with other kde-apps, which offer dropdown completion boxes.

I also tried to set the text completion to "Dropdown List & Automatic" but it didn't help.
The only working thing is when I just set it to "Automatic", but then I loose to completion box, and only see one completed entry.
Comment 1 MaxAuthority 2004-07-24 03:45:17 UTC
tested it again with cvs version from 07/20/04.

Now it works at least, when I set the "text completion" mode in the context menu to "dropdown & automatic".

However, the settings, which completion mode I like for text-boxes is not saved when I restart konqueror, which makes this feature useless.
Comment 2 Marijn Schouten 2006-04-17 19:57:26 UTC
is this still the case?
Comment 3 MaxAuthority 2006-04-17 20:45:50 UTC
Yes, just tested with 3.5.1
Comment 4 Leo Savernik 2006-04-20 23:19:47 UTC
This used to work up to and including KDE 3.0. Then it was disabled intentionally. Thus let's gather votes for this bug to signal that the current implementation is considered inconsistent with other completion boxes throughout KDE (most notably the location bar's and minicli's).
Comment 5 Michael Leupold 2008-04-06 08:20:59 UTC
Created attachment 24224 [details]
testcase

Just a simple form to test the behavious. Not sure if needed, adding anyway.
Comment 6 Michael Leupold 2008-04-06 08:21:57 UTC
Confirmed in trunk r794020.
Maybe make this a wish if it was disabled intentionally.
Comment 7 Dawit Alemayehu 2011-06-14 02:45:21 UTC
All the issues mentioned here have been fixed a long time ago. None of this is valid in the current versions of KDE (v4.6).
Comment 8 Dawit Alemayehu 2011-06-14 02:46:13 UTC
Wrong bug report. Sorry...
Comment 9 Myriam Schweingruber 2012-06-18 18:08:01 UTC
Message from the Bugsquad and Konqueror teams:
This bug is closed as outdated, as we do not have the manpower to maintain the KDE3 version anymore.
If you still can reproduce this issue with Konqueror 4.8.4 or later, please open a new report.
Thank you for your understanding.
Comment 10 Leo Savernik 2012-06-19 08:52:36 UTC
If you had checked the testcase, you'd have noticed that the bug still exists 
in KDE 4.x. Therefore, I'm reopening.
Comment 11 Leo Savernik 2012-06-19 08:58:38 UTC
For some reason bugzilla doesn't let me change the version field. Consider 
this bug still to be valid for the 4.x series.
Comment 12 Myriam Schweingruber 2012-06-19 10:39:12 UTC
(In reply to comment #10)
> If you had checked the testcase, you'd have noticed that the bug still
> exists 
> in KDE 4.x. Therefore, I'm reopening.

Well, I am sorry, but there are 1800+ open bugs I simply can't check all of them. Since this was never confirmed to still happen in the 4.x series and comment #7 suggests it was not reproducible in the 4.x versions I closed it.

It is nice you did check, could you please specify which exact version this is last reproducible with?
Comment 13 Leo Savernik 2012-06-19 20:27:57 UTC
Am Dienstag, 19. Juni 2012 schrieb Myriam Schweingruber:
> comment #7 suggests it was not reproducible in the 4.x versions
Comment 8 nulls comment 7.

It's definitely not fixed in 4.4.5, other people may easily check more recent 
versions by the handy testcase kindly contributed by Michael Leupold.

I'd be really surprised if this bug had been fixed since then as I'm closely 
monitoring the kfm-mailing-lists and commit-lists and haven't spotted any 
related commit.
Comment 14 Myriam Schweingruber 2012-06-20 09:15:37 UTC
Leo: it is pretty pointless to test with 4.4.5 which is totally outdated, so is this still valid with 4.8.4, yes or no?
Comment 15 Leo Savernik 2012-06-20 22:24:36 UTC
First, thanks of taking care of potentially outdated bugreport. But in this 
case I have to protest.

It is not pointless! You wanted a check whether the case is still true for the 
4.x series. It is!

The codebase has *not* been rewritten since 4.4.5 and 4.8.4, there'd been no 
chance that the bug had magically fixed itself. This bug is still valid unless 
proven the opposite by applying the testcase.

It is hilarious to declare a two year old version "totally outdated".
Has there been a rewrite? No.
Has there been a relevant commit? No.
Is khtml's code base changing fast and revolutionarily? No.
Code tends to survive a very long time, typically way longer than two years.

So please do not close bugs simply to rack up high numbers in bug squashing. 
We aren't a corporation, we are no managers, we don't need that kind of self 
delusion. Only fixed bugs count.
Comment 16 Myriam Schweingruber 2012-06-21 11:36:53 UTC
Well, according to the developers it is outdated, as currently not a single distribution still ships this version.
Comment 17 Andrew Crouthamel 2018-11-09 01:07:41 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 18 Andrew Crouthamel 2018-11-20 04:01:52 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 19 Justin Zobel 2022-12-31 00:24:17 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 20 Bug Janitor Service 2023-01-15 05:10:04 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 21 Bug Janitor Service 2023-01-30 05:06:49 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!