Issue 35973

Summary:	Toolbar Menu: fixed string "Can't Undo"
Product:	General	Reporter:	ulf.stroehler
Component:	code	Assignee:	AOO issues mailing list <issues>
Status:	ACCEPTED ---	QA Contact:
Severity:	Trivial
Priority:	P3	CC:	biczoa, eric.savary, issues, kpalagin
Version:	680m58
Target Milestone:	AOO Later
Hardware:	All
OS:	All
Issue Type:	DEFECT	Latest Confirmation in:	---
Developer Difficulty:	---

Description ulf.stroehler 2004-10-21 17:37:14 UTC

REPRODUCTION:
=============

1. edit smthg. e.g. in Writer, so that Undo buffer gets filled with smthg.
2. resize the Office root window, so that the Undo *icon* in the toolbar becomes
invisible
3. open the toolbar's menu (to see covered menu items)

=>Notice the string "Can't undo", which is obviously wrong.

us->cd: pls. clarify with UserEx. whether they could accept our suggestion to
shorten the string to simply "Undo" (as talked about on the phone together with
DVO).
Thx.

Comment 1 carsten.driesner 2004-11-09 08:39:45 UTC

CD: Accepted.

Comment 2 hba 2007-05-17 17:27:03 UTC

The same applies to the Restore (Can't Restore) button (ie it is incorrectly 
captioned in the toolbar's menu when the window is shrunken so that the 
toolbar cannot accomodate it).

This is potentially dangerous behaviour. If a user inadvertently modifies or 
erases irreplaceable data, the misleading caption may stop him or her trying 
to reclaim it and the data will really be lost.

However, an experienced user may notice that the button is enabled (despite 
the caption).
Also, a desperate user is likely to try pressing the button anyway.

Comment 3 rekt 2008-10-15 04:31:47 UTC

I just ran into this problem.  It is definitely confusing, especially since when
the undo icon in the toolbar is visible, its tooltip is eminently sensible. 
Shouldn't the expanded icon text just be the same as the tooltip?

Comment 4 edeku 2009-01-12 09:33:25 UTC

There is the same problem with the "Restore"-button. This is quite confusing to
new and clueless users and should be fixed soon.

Comment 5 kpalagin 2009-11-10 15:59:17 UTC

*** Issue 44243 has been marked as a duplicate of this issue. ***

Comment 6 kpalagin 2009-11-10 16:01:13 UTC

issue still present in 3.2.
Any chance to fix this for 3.3?

Comment 7 eric.savary 2009-11-10 16:39:04 UTC

@kpalagin: not sure it was a good choice to close issue 44243 as dup because
there you find some discussions between Liz (UserEx) and CD (Dev). Not here...

Else to answer your question: I don't think we have the time to care about such
a not so severe issue for 3.3. But who knows...
There's a CWS swundo05 which has no target but should contain such fixes.