Bug 350787

Summary:	TAB key on recipient list should move to next field
Product:	[Applications] kmail2	Reporter:	skaumo
Component:	composer	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED WORKSFORME
Severity:	normal
Priority:	NOR
Version:	5.6.3
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description skaumo 2015-07-30 11:55:33 UTC

Steps to reproduce:

- compose a new mail
- enter the "To" field and start typing
- autocompletion begins, and returns a list of addresses
- select an address with the arrow keys (up/down)
- press TAB

Expected behaviour: cursor to move on to next "To" field
Actual result: next item in the list is selected.

I didn`t notice, and sent an e-mail to the wrong recipient. Could have been sensitive information.

I`ve never seen the TAB character moving forward or backwards in a dropdown list, especially not in a form. TAB should only move between fields.
Please fix this behaviour



Reproducible: Always

Steps to Reproduce:
- compose a new mail
- enter the "To" field and start typing
- autocompletion begins, and returns a list of addresses
- select an address with the arrow keys (up/down)
- press TAB


Actual Results:  
next item in the list is selected.


Expected Results:  
cursor to move on to next "To" or "Cc" field


I didn`t notice this behaviour, and sent an e-mail to the wrong recipient. Could have been sensitive information.

I`ve never seen the TAB character moving forward or backwards in a dropdown list, especially not in a form. TAB should only move between fields, and arrows or PGUP/PGDN should navigate in the list

Please fix this behaviour

Comment 1 Denis Kurz 2017-06-23 20:03:41 UTC

This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.

Comment 2 Denis Kurz 2018-01-31 16:53:37 UTC

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

Comment 3 skaumo 2018-02-09 22:04:06 UTC

This is still happening on kmail-17.08.3:5, kdepim-meta-17.08.3-r1


How about leaving this ticket open? Even users may not have the manpower to keep reopening duplicates of old tickets the same way the KDE team may not have the manpower to close them.

Comment 4 Christoph Feck 2018-02-23 00:13:53 UTC

Thanks for the update; changing status.

Comment 5 Justin Zobel 2022-11-15 22:58:51 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 6 Bug Janitor Service 2022-11-30 05:14:30 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 7 Bug Janitor Service 2022-12-15 05:14:40 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!