https://bugs.documentfoundation.org/show_bug.cgi?id=141747
--- Comment #18 from Mike Kaganski <[email protected]> --- Let me describe a bit more what I already wrote: (In reply to Mike Kaganski from comment #11) > ... something like > word count / spell check); when the orphaned items are found, there could be > some information shown to user (it could be an infobar; or an icon on status > bar; or whatever (not too intrusive) UX invents...), to allow them open and > inspect the orphaned list. So the timing is like this: 1. User types. 2. At the same time, asynchronously, a check is on-going, if there are any orphaned elements. 3. User presses Del, and removes something that is referenced elsewhere. 4. User keeps typing, and types a couple (maybe 10) more words. 5. A few seconds later, the background check from #2 finds a newly orphaned item. 6. *Some* indication appears: a balloon tip, an infobar, anything - that orphaned item is found, with a way to see a list of all orphaned items, navigate to them in the document, and maybe undo a few keypresses if needed. Since it is close to the point when the problem was created, the user can see where the problem was. Since it's asynchronous, it doesn't block every keypress. And there's no need to force user to find anything. And the solution is not limited to any special case: e.g., it would also find already orphaned items crated in older versions without such a check, or in master documents after the fact. -- You are receiving this mail because: You are the assignee for the bug.
