Issue 99799 - Misleading "Cancel" when displaying the document recovery window at startup
Summary: Misleading "Cancel" when displaying the document recovery window at startup
Status: CLOSED DUPLICATE of issue 104466
Alias: None
Product: General
Classification: Code
Component: ui (show other issues)
Version: OOo 3.0.1
Hardware: Unknown All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: thorsten.martens
QA Contact: issues@framework
Depends on:
Reported: 2009-03-03 04:00 UTC by ccheney
Modified: 2009-09-14 14:16 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description ccheney 2009-03-03 04:00:39 UTC
The user thinks that 'Cancel' is confusing and could cause someone to think to
cancel loading openoffice instead of cancel recovery of the document. Perhaps
changing Cancel to Cancel Recovery or something like that would be more obvious
to the user?

From the Ubuntu bug report:

When openoffice has been killed without document changes saved, and then started
up again, a document recovery window appears and you have the option to "Start
Recovery" or "Cancel." Since you just started openoffice, when you read the
"Cancel" option it is very likely you will think it means that you are going to
cancel the opening of openoffice which you don't want to do. If the message said
something like, "Don't recover." and in the text above that explains these,
"Don't recover, if you would rather never recover the documents below." or
something like that. You are likely a good word smith, and can improve on it,
but the present "Cancel" is misleading.

This is even more annoying because if you read a document from the web that is
stored in /tmp and then you reboot, that file doesn't exist, and so it remains
on the list to recover, but fails every time. What you really need to do is
press "Cancel," but that sounds so much like saying "I don't want to open
openoffice that you just keep dealing with the recovery window. At least I did!
Comment 1 mairin 2009-08-24 16:19:05 UTC
I can't figure out how to make my bug,, a duplicate of this
bug. I included a screenshot and mockup in my bug so it might be worth looking at.
Comment 2 caolanm 2009-09-14 14:13:22 UTC
I'll mark it as dup of mairin's mockup

*** This issue has been marked as a duplicate of 104466 ***
Comment 3 caolanm 2009-09-14 14:16:18 UTC
close this as a dup