Problem

• create a task
• add a reviewer
• login as the reviewer, modify some segment content
• This editing adds TrackChanges markup then
• Change the role of the user to translator
• this changes then the tasks workflow step translation
• After that open the segment again as above user (now as translator)
• Now the TrackChanges handlers are not triggered
  • there is a function which checks if track changes should be used, basing just on the workflow steps

Solution

Although this problem is mostly academic, we should fix it, because TrackChanges markup may be destroyed on that way. The only senseful solution: In addition to the above mentioned workflow step check, TrackChanges should also be activated in a task, if at least one segment with track changes was saved. This could be done by a new flag "useTrackChanges" flag in the task meta table, which is by default false, and is set to true if it was false and the first segment with TrackChanges is saved. This flag is evaluated in the check function too.