202242 - no undo in bookmarks

Status: RESOLVED WORKSFORME

(SeaMonkey :: Bookmarks & History, defect)

Description

[Walter Haidinger]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4a) Gecko/20030402
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-AT; rv:1.3) Gecko/20030312

The undo in bookmarks edit menu (Ctrl-Z) never works,
i.e. is always greyed out.

No changes can be reverted. This is especially bad if you
accidently delete some bookmarks by hitting the del-key.
Mozilla seems to commit bookmark changes immediately to the 
bookmarks.html file so the entry is lost unless you have a backup.


Reproducible: Always

Steps to Reproduce:
1. open bookmark manager
2. select a bookmark or a bookmark folder
3. either do delete, cut or copy&paste
4. then try to select undo from the edit menu

Actual Results:  
Undo (Ctrl-Z) cannot be selected, it is greyed out.

Expected Results:  
Allow to select undo and revert the changes

Notes:
* This _may_ to be a duplicate of bug #155486 which was entered for MacOS.
* No problems in my CVS build of Mozilla under Linux 
  [Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4a) Gecko/20030402]
  where there is an additional Redo menu entry too

Comment 1

[Jo Hermans]

Eh .. in Mozilla 1.4, it's exactly the opposite. See bug 199367.

Comment 2

[Walter Haidinger]

Well, not quite. Despite Undo/Redo should be grayed out, it
seems to work under the specified build for Linux noted above.

However, not always... I just checked and could not undo anything.
This is not reproducable (unlike under Windows) though. 
After restarting mozilla undo/redo works again. Odd.

Comment 3

[Walter Haidinger]

Update: Just installed the german 1.4a build 
(mozilla-win32-1.4a-deAT-talkback.zip from mozilla.kairo.at) 
which features the redo menu item too: Undo works.
The bug seems to be fixed in the 1.4 alpha tree.

Comment 4

[Henrik Lynggaard Hansen]

also seen working on my windows 2000:
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030412

This buildl is newer than the one reported against.

Reporter could you use a more recent build and retest of the bug still persists ?

Comment 5

[Walter Haidinger]

As I wrote in comment #3:
The bug seems to be fixed in the 1.4a release.

Comment 6

[Henrik Lynggaard Hansen]

per comment #5 im marking this works-for-me