Modifications to Cc list can show 'removed' in comment even if no one was removed

[ryano@…]

The following conditions cause a modification to the cc field to display removed, even if no one was removed from the cc list.

Suppose I have a cc list that ends with a trailing comma. For example: randys, kenl,

I change the list to display: randys, kenl, boyde. I then see as shown in the attached screen capture:

• cc boyde added; removed

However, if the cc list is: randys, kenl, boyde (note that there is no trailing comman to the cc list), then changing to: randys, kenl, boyde, allano I get:

• cc allano added

[Ryan J Ollos]

CC List Bug

[ryano@…]

Here is the screen capture:

[ryano@…]

On further inspection I believe the removed entry results because whitespace is being removed from the Cc list.

[Ryan Ollos <ryano@…>]

Seems like the best way to deal with this issue would be to remove trailing commas and whitespace before setting the Cc field. That should just be a few lines of code, right? I'm just starting to learn python, but if someone points me to the file where this is handled, I'd try working on a patch.

[Ryan Ollos <ryano@…>]

One other useful bit of information: On my Trac instance, when I add a list of comma separated keywords to the Keywords field, where the list has a trailing comma, I can see the trailing whitespace and comma are removed and the text box updated when the page is submitted.

I added a list of keywords with a trailing comment to this ticket, and I don't get the same behavior. However, the keywords field on this Trac instance does seem to behave appropriately, and does not exhibit the same behavior as the CC field on my Trac instance (0.11.4). See comment:3 and comment:5.

I suspect the behavior I see with the Keywords field on my Trac instance is due to having the ​KeywordsSuggestPlugin installed (version on trunk patched with keywords.patch from ​ticket 4201).

[Ryan Ollos <ryano@…>]

Another piece of information: I'm using the ​AutocompleteUserPlugin, which appends a comma and a whitespace each time you add a username using the autocomplete function. I suspect the underlying problem I'm reporting in this ticket is an issue with Trac, but since I'm using the AutocompleteUserPlugin I see the behavior all the time, whereas users on a Trac instance without the AutocompleteUserPlugin may rarely see the behavior (unless they are in the habit of appending a comma to the user list in the Cc field).

To directly edit the Cc field appears to require TICKET_EDIT_CC permissions, which all users have on my Trac instance, but it doesn't look like I have that permission for Edgewall's Trac. Perhaps someone with the requisite permissions can try to reproduce the behavior on Edgewall's Trac.

[Christian Boos]

testing…

[Christian Boos]

Mmh, okay.

[Christian Boos]

(leaving randys and kenl alone :-) )

[Remy Blank]

I'll take care of this.

[Remy Blank]

Fixed in [10013], for both ticket creation and update.