https://bugs.documentfoundation.org/show_bug.cgi?id=166723
--- Comment #29 from Tuomas Hietala <[email protected]> --- (In reply to Eyal Rozenberg from comment #21) > Remember: "Rejection" or "Acceptance" of changes are actions which vanishes > a proposed ("tracked") change. If the change is accepted - the underlying, > untracked, document changes; if the change is rejected - the underlying > document does not change. I would guess this ("Reject and Accept both make the proposed change vanish, so they're closely related") is the way users typically think about change tracking. > The action we're discussing is an _acceptance_, not a _rejection_. After the > acceptance, a reversion is introduced as a tracked change. I suppose "Accept, then revert" the would then be the most technically correct description for what happens 'under the hood'. But I don't think it would make sense for the average user who is not a developer or LO power-user. > "Reject but track" would mean a NO-OP. The word "but" is not a logical operator. It's a modifier here; we reject the change, BUT with some qualifications: unlike the usual "Reject" function, we keep tracking the change. OTOH something like "Accept, but revert" would likely sound confusingly contradictory to the average user; a bit like "paint the fence black, but white". -- You are receiving this mail because: You are the assignee for the bug.
