After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 256210 - Unable to see marked adresses in "To", "CC" and "BCC"
Unable to see marked adresses in "To", "CC" and "BCC"
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Contacts
unspecified
Other All
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2004-03-30 08:12 UTC by Lasse Bigum
Modified: 2004-04-01 22:03 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Lasse Bigum 2004-03-30 08:12:22 UTC 
Description of Problem:


Steps to reproduce the problem:
Try typing something into the mentioned fields, 
and mark it with the keyboard, no highlight shows

Actual Results:
No highlighting occurs

Expected Results:
Highlighting

How often does this happen? 
Every time
Comment 1 Gerardo Marin 2004-03-30 20:11:58 UTC 
What Evolution version is this?
Are you using LDAP or local folder contactacts?
Do your contacts show in addressbook?
Comment 2 Gerardo Marin 2004-03-30 20:12:20 UTC 
Please reopen this report when you reply.
Comment 3 Lasse Bigum 2004-04-01 08:41:34 UTC 
I don't think it has *anything* to do with my contacts, it's simply 
the field that doesn't "support" highlighting.

It's all local contacts, and I'm using 1.4.5

What I mean is: try typing "asdsadsa" in the "To" field, and then 
marking it with the keyboard (CTRL+SHIFT+LEFT)....you can't tell it's 
marked. Try doing the same with the "subject" field, and it works 
fine.

The "highlighting" works though, if I mark something and press DELETE, 
it deletes it properly.
Comment 4 Gerardo Marin 2004-04-01 21:59:08 UTC 
Works for me in 1.4.6. 
Please upgrade and reopen if still doesn't work for you.
Closing as hopefuly fixed.
Comment 5 Lasse Bigum 2004-04-01 22:03:02 UTC 
What the ****!?

:-)

I'm *soooo* sure this didn't work previously....I'm on Debian, so it 
must have upgraded to 1.4.6 which had a fix, since I am *sure* 1.4.4 or 
1.4.5 had the bug.

Oh well, you guys are awesome. Got to love debugging software when you 
get replies and fixes THIS fast :-)

Keep up the good work!