Suppose last time I ran LO, it crashed while working on an unsaved document foo. Now, I'm running LO again, but - I do so by opening some other document, bar and baz. If I were to only start LO, I suppose it can make sense for me to be required to finish considering document recovery before I do anything else (although TBH I'm not even sure about that.) However, if I opened bar - this decision will not be affected by anything I do w.r.t. recovery; so I don't see why the opening of bar should wait until after I've chose whether to recover or not. Certainly, the recovery dialog can get focus and placed on top to draw attention to it; but bar and baz should be opened in the background.
I can see how users might want to go straight to the document they set out to start working on, so setting to "new", but wondering what the UX team thinks of being able to use LO while a recovery dialog is put aside.
(In reply to Stéphane Guillou (stragu) from comment #1) > but wondering what the UX team > thinks of being able to use LO while a recovery dialog is put aside. It's just a window on the side...
Reasonable request but what do we do in case the application is started with the very same document that crashed last time? Could imagine to show the recovery dialog first in this case and non-modal in all other situations.
It sounds like a bad idea to me.
(In reply to Heiko Tietze from comment #3) > Reasonable request but what do we do in case the application is started with > the very same document that crashed last time? Could imagine to show the > recovery dialog first in this case and non-modal in all other situations. This bug is only about when we try to open LO with a different document. In the case you describe, I agree. Note also there might be several recoverable files; opening any one of them could make the dialog modal. (In reply to Justin L from comment #4) > It sounds like a bad idea to me. It would be useful if you explained why. I gave motivation in the opening comment.