Bug 103807 - New composer style in 3.4 is unusable when a "BCC address" is set for the identity
Summary: New composer style in 3.4 is unusable when a "BCC address" is set for the ide...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail
Classification: Applications
Component: composer (show other bugs)
Version: 1.8
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2005-04-13 18:20 UTC by Oded Arbel
Modified: 2015-04-12 10:07 UTC (History)
1 user (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 Oded Arbel 2005-04-13 18:20:26 UTC
Version:           1.8 (using KDE 3.4.0, Mandrake Linux Cooker i586 - Cooker)
Compiler:          gcc version 3.4.3 (Mandrakelinux 10.2 3.4.3-7mdk)
OS:                Linux (i686) release 2.6.11-6mdk

The new "Mozilla like" KMail composer style is completely unusable if the user has his identity set with a "BCC Address".

When a BCC address is set, and the composer opened, the BCC address is set as the first field which is also the field having the focus.
The second field default's to "Cc" for some weird reason, and it takes 3 <TAB> actions to get to it (!!).

The former 3.3 behavior where when a "BCC address" was set in the identity was vastly superior:
* The BCC field would only be visible if the composer has "bcc" checked in the view menu, so unless I specifically wanted to view or modify it I didn't have to bother.
* The BCC field would be the last address field
* The field having the focus when the composer starts was the "To" field
* A single <TAB> action would take you to the next field.

Now, as I have "BCC address" set in my indentity dialog, when I compose a new email, instead of immediately starting to type the address of the recipient, I have to:
- move the mouse over to the field type of the *second* address field.
- change it to "To" by either opening the drop down or scrolling over it (nice workaround for a problem that should never have happened).
- use the mouse to move the focus to the *second* address field.
- type away.
Or
- Hit Tab
- Hit Tab
- Hit Up-Arrow
- Hit Tab
- Type away

The composer is now also much too complicated for its own good when you "reply all" to an email with many addressees. In 3.3, that complication was hidden by having long texts in the address fields clipped, and having multiple addresses in a single field remain as in the original mail. But now it separates each address to a field of its own and has a **scroll bar** ! And way too many widgets that require attention - ouch.
Comment 1 Oded Arbel 2005-06-27 19:01:15 UTC
In the current version I'm using (latest 1.8.1 package from Mandrake cooker), when opening a new composer, the second address field (which is also the first which is empty and available) is set by default to "To" which is better then in the above description (although its still a mess).

Comment 2 Matt Douhan 2005-07-20 13:43:20 UTC
Yes I fixed this during our PIM meeting in the netherlands, I will look into fixing the layouting as well so that the to gets on top of the bcc and thus is the first available field in the view.
Comment 3 Oded Arbel 2005-07-20 16:13:06 UTC
It would also be nice if <TAB> will skip the "clear" buttons (they are useful control elements to point a mouse at, but if you already have the cursor in the field and your hands on the keyboard, deleting is done more naturally by the keyboard), and possibly only move through the address field - skipping also the "to/cc/bcc" selectors.
Comment 4 Daniel Hahler 2007-01-26 20:23:32 UTC
I think the initially bug has been fixed with 1.9.6 and/or I don't know how to reproduce it.
The "Clear" button does not get skipped when TABbing.
That should probably become an own entry or just get implemented in some minutes.. ;)
Comment 5 Oded Arbel 2007-12-04 21:28:36 UTC
I'm using 1.9.6 (although much less then in the past as the mail composer dialog is not nearly as useful as Evoltion's composer which - surprise - behaves like KMail 1.7's did). With 1.9.6 all the problems described above still exist, including tabbing through widgets that has no business being in the tabbing order. 

The second field's To vs Cc issue is funny - because apparently the second field is set to whatever it was set to when you last had a mail composer open: start a new mail and change the second field to Cc and close the composer (say "discard" to the close dialog), and open it again - its set to Cc still. Change it to To and close the composer, open it again and its set to To. quite interesting, but still useless - of course the first editable field should be To: when did you last sent an email where you first specified the Cc recipients and only later the To recipients ?
Comment 6 Michael Leupold 2008-09-14 21:11:43 UTC
I just checked in KMail 1.10.90 (KDE 4.2trunk) and some of the behaviour is still there. BCC is becoming the first textline again. The clear buttons however are now skipped on Tab.
Comment 7 Laurent Montel 2015-04-12 10:07:49 UTC
Thank you for taking the time to file a bug report.

KMail2 was released in 2011, and the entire code base went through significant changes. We are currently in the process of porting to Qt5 and KF5. It is unlikely that these bugs are still valid in KMail2.

We welcome you to try out KMail 2 with the KDE 4.14 release and give your feedback.