https://bugs.documentfoundation.org/show_bug.cgi?id=166790
Eyal Rozenberg <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |83946 --- Comment #3 from Eyal Rozenberg <[email protected]> --- (In reply to Miklos Vajna from comment #2) > That's kind of intentional, you are meant to use reinstate only on redlines > that is authored by somebody else. Why? 1. That's not what the blog post suggests would happen. 2. Remember that, often, more than one person uses the same LO installation with the same username. This happens on family computers on which different people don't bother to define users of their own, or on office computers where the user is not really associated with anyone in particular. 3. See below > So if you have some content, somebody > else wants to delete it, then you can press reinstate to introduce it again. > Not sure what's the best way to communicate this better, perhaps disable the > action in case the cursor is inside a redline that you yourself authored? That would improve consistency; but... 3. Why not just allow treating "your" own changes just like the changes by another person? What you're saying is that, right now, there is no desired action intended for the case of "reinstate"ing your own changes, so much so that you'd be willing to disable it. Well, we can choose such an action, and a better choice of such action is doing the same thing "reinstate" would do to changes by others. I believe it is better to keep consistency of actions on changes irrespective of authors, than to introduce it with this action. Even if the motivation for the feature is tracked changes by others. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=83946 [Bug 83946] [META] Tracking changes issues -- You are receiving this mail because: You are the assignee for the bug.
