Closed Bug 239910 Opened 20 years ago Closed 12 years ago

undo removes last bookmark added but redo does not work

Categories

(SeaMonkey :: Bookmarks & History, defect)

x86
All
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: mcantrell, Unassigned)

Details

(Whiteboard: [2012 Fall Equinox])

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7b) Gecko/20040316
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7b) Gecko/20040316

In the browser, if you click ctrl-z to undo the last action but are not in a
text field, the most recently added bookmark is removed.  However, redo is
disabled -- you cannot press it's key combination of ctrl-y nor can you select
it in the menu.

If you open up the bookmark manager, redo is properly activated, and hitting
ctrl-y or selecting it replaces the bookmark.

Reproducible: Always
Steps to Reproduce:
1. Click away from any text field.
2. Press Ctrl-Z (Observe bookmark dissapearing from Personal Toolbar window)
3. Press Ctrl-Y (Observe no change)

Actual Results:  
Nothing happened after hitting Ctrl-Y.  The software did not respond.

Expected Results:  
After hitting Ctrl-Y, the "undo" of the bookmark should have been reversed, and
the bookmark should have been re-added.
I see this on LInux 2004051006.
Note you can redo by going to Bookmark manager then using the menu b/c the
shortcut key does not work there.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows XP → All
Product: Browser → Seamonkey
Reassigning as per Bug #32644
Assignee: p_ch → nobody
Can you reproduce with SeaMonkey v2.0rc1?
WFM here, now in step 2 bookmark is not removed, and if you press Undo in Bookmarks Manager, Redo works just fine
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:18.0) Gecko/18.0 Firefox/18.0 SeaMonkey/2.15a1
Build identifier: 20120921003032
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Whiteboard: [2012 Fall Equinox]
You need to log in before you can comment on or make changes to this bug.