https://bugs.documentfoundation.org/show_bug.cgi?id=154466
--- Comment #2 from [email protected] --- (In reply to ady from comment #1) > I'm not sure that having an "undo" question is much less disruptive than > having the confirmation question. Both require an answer from the user, or > alternatively either of them could be disabled by user's options. The user's flow would be different: Confirmation question: Always requires a click to answer (to overwrite data or not to overwrite). Notification + undo: If the user intends to overwrite data, just do nothing after the paste; otherwise it's just one click to undo. > > There are at least 2 differences though: the potential "undo" implies: > > * a requirement for every single result to be correctly undone (and we know > by experience and bug reports that this does not always work as expected); I think this is an excuse for not having a better UX. > * in case we either revert the action or we don't confirm the pasting > action, the initial step: > > ** before the "undo" question, already used resources to actually paste > whatever we copied, and more would be used in case we revert; whereas, > ** the current "confirmation" dialog asks before wasting those resources. Unless the data is really large (say, megabytes or more), the resource cost is negligible. Computers are already fast enough, while the user would at least take 0.5 seconds to read and answer the confirmation question. -- You are receiving this mail because: You are the assignee for the bug.
