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 330448 - Mistakes Made On New->Meeting Screen Not Cleared Fully
Mistakes Made On New->Meeting Screen Not Cleared Fully
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Calendar
2.6.x (obsolete)
Other All
: Normal major
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks: 327508
 
 
Reported: 2006-02-08 18:07 UTC by David Richards
Modified: 2013-09-13 00:52 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Mistakes made on first screen are still in array somewhere (336.26 KB, image/png)
2006-02-08 18:08 UTC, David Richards
  Details
movie showing how to easily reproduce (346.94 KB, application/x-shockwave-flash)
2006-02-15 14:08 UTC, David Richards
  Details
Fixes the bug (1.92 KB, patch)
2006-03-03 14:51 UTC, Chenthill P
committed Details | Review

Description David Richards 2006-02-08 18:07:39 UTC
Please describe the problem:
Ok, this one has been hard to find, and I finally figured it out.

If you are in the New-->Meeting screen and entering users into the main screen,
no matter what you type it will take it because obviously for outside email
addresses there is no way to verify that they are correct.  However, if you make
a mistake and load the screen with the item, and then click focus into that same
item and make the correction the wrong item isn't removed from the storage
array.  It's gone from the first screen, but it's still loaded in memory.  If
you click on [Attendees] you can see that it's still there.

Even though the message looks ok, if you click the Save icon, the message will
not send and alerts you of an invalid user ID.  It's trying to send the errant
entry, even though you can't see it anywhere.  The screen attached will show you
proof that it's still in memory.

Steps to reproduce:
1. Select New-->Meeting
2. Click [Add] to add another attendee and then type "jdkfjdkf" and then hit ENTER
3. Click back into that same area and enter a valid email address.
4. Click the [Attendees] button it should only display those two names, but the
original "jdkfjdkf" is still loaded in memory.

Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 David Richards 2006-02-08 18:08:15 UTC
Created attachment 58952 [details]
Mistakes made on first screen are still in array somewhere
Comment 2 Poornima 2006-02-15 06:21:26 UTC
David: I am not able to reproduce this bug on evolution 2.5.9. Is this consistently reproducible ?
Comment 3 David Richards 2006-02-15 14:07:33 UTC
I can easily and always reproduce this bug.  I'm attaching a shockwave movie of the method to reproduce.

In the movie:
1) Select new-->Meeting
2) Click [Add] and in the single line widget enter "jjjjj" and then {Enter}
      (It takes it, because it can't verify outside addresses)
3) Click focus back into the area where I typed "jjjj" and type in "harold", it then autocompletes and I arrow down to his name and hit {Enter}.  Everything appears to be OK.

But if you try and send the meeting, it says "Invalid ID" and won't let you send.  The reason can be seen.  In the movie I then click on "[Attendees]" and the "jjjjj" is still there and displaying.  I take the mouse pointer and show where it's displayed.
Comment 4 David Richards 2006-02-15 14:08:54 UTC
Created attachment 59410 [details]
movie showing how to easily reproduce
Comment 5 David Richards 2006-02-17 14:36:07 UTC
still broken in 2.5.91, this is a pretty nasty little bug, causing lots of problems here.
Comment 6 Srinivasa Ragavan 2006-02-17 16:07:29 UTC
confirming the bug
Comment 7 David Richards 2006-02-28 21:48:00 UTC
Bumping to major.  This is a showstopper.  Harish said on IRC he had a fix for this but it didn't make it to 2.5.92.   All of our test users are stumbling on this one.  Easy to recreate.
Comment 8 Chenthill P 2006-03-03 14:51:36 UTC
Created attachment 60566 [details] [review]
Fixes the bug
Comment 9 Srinivasa Ragavan 2006-03-03 17:39:21 UTC
chenthill. Looks good to commit. Just send to the list and get it OKed for a second opinion :) since we are approaching hard freeze.
Comment 10 Chenthill P 2006-03-06 07:24:52 UTC
Fix has been committed.