Magnus, bugzilla wouldn't let me set Jorg as the reviewer like I normally do due to PTO. Here's a patch to fix the regression. I've tested it and it works well. It also fixes this issue described in the previous comment 18: >So with the "try" code, when a privileged user (user-a) sets a tag on a message it will be seen in the shared folder by users who can't store tags on the server (e.g., user-b). If user-b removes the tag, it will come right back since user-a has not yet removed it from the message in the shared folder on the server. This seems OK. But if user-a does remove the tag from the message on the shared folder, user-b will still see it. For user-b to not see the tag, it will have to be removed first by user-a and then later by user-b. Not sure if this is a big problem. Now when user-a removes the tag, user-b will automatically no longer see the tag and not have to remove it manually. Manuel and/or Mikhail: If you want a "try" build to test with this patch, let me know.
Bug 1596371 Comment 19 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Magnus, bugzilla wouldn't let me set Jorg as the reviewer like I normally do due to PTO. Here's a patch to fix the regression. I've tested it and it works well. It also fixes this issue described in the previous comment 18: >So with the "try" code, when a privileged user (user-a) sets a tag on a message it will be seen in the shared folder by users who can't store tags on the server (e.g., user-b). If user-b removes the tag, it will come right back since user-a has not yet removed it from the message in the shared folder on the server. This seems OK. But if user-a does remove the tag from the message on the shared folder, user-b will still see it. For user-b to not see the tag, it will have to be removed first by user-a and then later by user-b. Not sure if this is a big problem. Now when user-a removes the tag, user-b will automatically no longer see the tag and not have to remove it manually. Manuel and/or Mikhail: If you want a "try" build to test with this patch, let me know. Edit: The feedback "minus" was unintentional.